Locust.
Locust is a load testing tool with scenarios written in plain Python. User behaviour is expressed as ordinary code rather than configuration, which makes complex conditional journeys straightforward to express.
Where Locust fits on a long engagement.
Because a Locust scenario is just Python, behaviour that is awkward elsewhere becomes ordinary. Users who branch based on a response, maintain session state across a long journey, or follow a distribution drawn from production data are all simply code, using whatever libraries are already available.
For teams already writing Python this removes the adoption cost entirely — the test is written in the language they use, reviewed by the same people, and runs on the same tooling. That matters more for whether performance testing actually happens than any feature comparison does.
What an assigned team does with Locust.
Load testing gets skipped because it is a separate skill in a separate tool that someone has to find time for. Removing the language barrier removes a real part of that friction.
The rest is making it routine rather than exceptional, which is a delivery-process question handled with the assigned capacity under outsource qa testing.
What we use Locust for.
- Journeys with real branching Conditional user behaviour expressed directly, without fighting a configuration format.
- Reusing existing Python utilities Authentication and data generation shared with the application's own tooling.
- Scaling out across workers Distributed runs coordinated from one controller when a single machine is not enough.
How Locust capacity is assigned.
Locust is usually chosen where the team's existing language makes it the lowest-friction option, so performance testing actually happens. Capacity for it is agreed as part of how the monthly fee is built.
Tell us what your roadmap needs Locust for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.