Tools whose documentation names load and performance tests
10 tools in the catalogue have a documentation page describing load and performance tests (traffic replay or synthetic load with latency and resource budgets). Licences: open-source 8, freemium 2.
Tools, alphabetical
| Tool | Licence | Hosting | Documentation page |
|---|---|---|---|
| Artillery | open-source | self-hosted, cloud | source verified 2026-10-21 |
| Drill | open-source | self-hosted | source verified 2026-10-21 |
| Gatling | open-source | self-hosted, cloud | source verified 2026-10-21 |
| Grafana k6 | open-source | self-hosted, cloud | source verified 2026-10-21 |
| hey | open-source | self-hosted | source verified 2026-10-21 |
| Karate | open-source | self-hosted | source verified 2026-10-21 |
| Locust | open-source | self-hosted | source verified 2026-10-21 |
| oha | open-source | self-hosted | source verified 2026-10-21 |
| Postman | freemium | cloud, self-hosted | source verified 2026-10-21 |
| TestMu AI (formerly LambdaTest) | freemium | cloud | source verified 2026-10-21 |
About the test class
Load and performance tests: catches N+1, pool exhaustion, cache storms, unbounded queries, autoscaling gaps; cannot catch functional defects, security, data correctness.
Questions
What is a Load and performance tests tool?
A tool whose own documentation describes load and performance tests: traffic replay or synthetic load with latency and resource budgets.
What tools are used for Load and performance tests?
Artillery, Drill, Gatling, Grafana k6, hey, Karate, Locust, oha, Postman and TestMu AI (formerly LambdaTest), listed alphabetically from their own documentation.
Which Load and performance tests tools are open source?
8 tools are recorded as open source: Artillery, Drill, Gatling, Grafana k6, hey, Karate, Locust and oha.
What is the difference between synthetic monitoring and end-to-end testing?
Synthetic monitoring runs scripted checks against production on a schedule (post-deploy); end-to-end tests run user flows against a deployed environment (pre-deploy, post-deploy). Synthetic monitoring cannot catch faults behind authentication the script does not reach.
How does a tool get into the catalogue?
A tool enters the catalogue when its own documentation names at least one of the 12 test classes, a pricing page or licence file exists, it has a dated release within 18 months, and every listed fact has a source URL with a verification date.
Why is a tool missing from the catalogue?
A tool is withheld when a gate fails: no documentation page names a test class, no pricing page or licence file, or no dated release within 18 months. 14 tool routes are withheld.