This week at work I was tasked with continuing some load testing that a previous Engineer had started. They had used locust which is an open source load testing tool to run the initial load testing on the staging environment. I now needed to do the same for production so I followed in their footsteps. - Source: dev.to / 8 days ago

Finally, let's compare the response time of the requests. For that, we will use Locust , an open source load testing tool. The tests will run for 5 minutes, and will increase 4 requests per second every second until they reach 1000 requests per second. - Source: dev.to / 3 months ago

Locust: Another open-source tool, Locust is particularly flexible due to its support for Python scripts. It can conduct load tests across multiple machines, making it possible to simulate millions of users simultaneously. An exceptional feature of Locust is its web-based UI, which allows real-time tracking of performance metrics during test execution. - Source: dev.to / 3 months ago

Locust is a perfect tool to use on such occasion:. - Source: dev.to / 4 months ago

So, in theory, we can handle 300 requests per minute on a single server which was the assumption we started with. After this, I decided to play with this configuration and see what we could achieve. But, to go ahead I need a system to measure the metrics of our load testing. So I quickly set up Locust on my system. Locust is an open-source easy to setup load-testing framework. - Source: dev.to / 4 months ago

On the continual testing side, We use ReadyAPI which allows API tests with multiple assercertions, good/bad paths etc. Really easy to manage (ours is curated by test team with very little coding experience). It can be set up to run on schedule or connected to CI/CD pipeline to run them all before merging new code. Source: over 1 year ago