Stressless: Stress Testing for PHP
Вставка
- Опубліковано 16 вер 2024
- Hello everyone! Welcome to another video on my UA-cam channel. Today, I'm excited to introduce you to the latest addition to the Pest PHP family: Stressless. This new stress testing plugin for Pest allows you to test your application under extreme conditions, such as dozens of concurrent users, and provides a detailed report of how your application performs.
- Get started with Pest and Stressless today: pestphp.com
- Stressless Documentation: pestphp.com/do...
----------------------------------------------------------------------------------------------------
Hi everyone! Want to see my videos before anyone else? Join as a member and get early access to all the new stuff I'm creating. It's a cool way to stay ahead and enjoy exclusive content. Can't wait to share it with you!
Join here: / @nunomaduro .
----------------------------------------------------------------------------------------------------
Let's keep in touch:
- Twitter: / enunomaduro
- Telegram Group: t.me/+RoAqqaaS...
- Threads: www.threads.ne...
- Mastodon: mastodon.socia...
- LinkedIn: / nunomaduro
- UA-cam: / nunomaduro
- GitHub: github.com/nun...
- Bluesky: bsky.app/profi...
- Tiktok: / enunomaduro
Thank you for the overwhelming feedback on the Stressless release. My goal is to make Pest the most complete testing framework in the world - all of this using my favorite language: PHP. Now, here are a few things I'd like to share about this plugin.
First, keep in mind that, just like the architecture plugin, we are just getting started with the potential of this package. We plan to add features that allow you to customize the stress test scenarios.
Scenarios can be stress test endpoints requiring authentication or test endpoints expecting a status different from 2xx.
Next, a question I've seen quite often is: what's the difference between testing an external domain vs testing a local IP address? Well, it depends on what you're trying to test.
When load testing a domain from an external network, you get a realistic picture of how your application performs under typical user loads. This includes factors like network latency and real-world internet traffic.
However, when testing a local IP address within your network, the focus is on understanding the performance of your internal infrastructure in a controlled environment, without external variables like internet or DNS resolution times.
It's particularly useful for identifying potential bottlenecks within your own network or server and for performance tuning of internal applications or servers. This includes tasks such as configuring PHP FPM more effectively, etc.
And that's it! I hope you've enjoyed this latest addition to the Pest family!
You're awesome. This is next level
see you next time🥳
thanks you for your works
It's good
Is this relevant for Laravel too?
*so sorry, I'm at very early level for now in programming
Yes, it's relevant for any web or API application that can be accessed via a domain or IP address.
thanks for the hard work!
I was wonder if there would be a way to use this to test as an authenticated user. For example login to the remote system and then do things authenticated users would do.
Eg. users logs in, registers for tournament, and sends invite to the team.
I know something like selenium/dusk would be needed at this level but just curious.
Thanks
It's on my plans add support for setup custom scenarios, such as testing endpoints requiring authentication or testing endpoints expecting a status different from 2xx.
What server is used when stress testing from a pest unit test?
Can you elaborate in your question?
Is there a way to collect and output measurements so we can run our own stats?
In theory, you can you use the stress function, outside of a test to actually grab those stats.
Please, please, please no background music for us with misophonia. If people want background music, they can put on their own radio.
Its possible to configure this in Github Actions?
Can i test post requests too?
We plan to add features that allow you to customize the stress test scenarios. Scenarios can be stress test endpoints requiring authentication or test endpoints expecting a status different from 2xx.