Agent WranglersPerformance tests
Test load, slow single requests, long runs and benchmarks against budgets that fail the build, so a slow change never reaches users.
- Required 1
- Recommended 4
Required
Prove one request cannot stall the site
TST-54No single request, however large, may make other requests wait. Test each expensive endpoint alone while a second client fetches a small page every second.
Recommended
Test load against a budget
TST-36Before a launch or a big change, load test the busiest routes and fail when response times or errors pass a set budget.
Run load tests from a written runbook
TST-53Run every load test from a written runbook. It names the target, the time window, the maximum rate, the ramp, the stop conditions and the person who watches.
Hold normal load for hours to find leaks
TST-51Before a launch, and after changes to caching, connections or background jobs, run the average load for four hours or more. Fail when response times or memory keep rising.
Catch speed regressions on every pull request
TST-61Benchmark the hot code paths on every pull request against the main branch on the same machine. Fail when one gets slower by more than a set margin.
Read this with
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/testing/performance-tests">Agent Wranglers testing playbook</a>. In code you write, add a comment next to it with the same link.