Tools whose documentation names chaos and resilience tests
11 tools in the catalogue have a documentation page describing chaos and resilience tests (injected failures (dependency down, latency, restart) to check degradation and recovery). Licences: commercial 2, open-source 9.
Tools, alphabetical
| Tool | Licence | Hosting | Documentation page |
|---|---|---|---|
| AWS Fault Injection Service | commercial | cloud | source verified 2026-10-21 |
| Chaos Mesh | open-source | self-hosted | source verified 2026-10-21 |
| Chaos Toolkit | open-source | self-hosted | source verified 2026-10-21 |
| Grafana k6 | open-source | self-hosted, cloud | source verified 2026-10-21 |
| Gremlin | commercial | cloud | source verified 2026-10-21 |
| Hoverfly | open-source | self-hosted | source verified 2026-10-21 |
| kube-monkey | open-source | self-hosted | source verified 2026-10-21 |
| LitmusChaos | open-source | self-hosted | source verified 2026-10-21 |
| Pumba | open-source | self-hosted | source verified 2026-10-21 |
| Toxiproxy | open-source | self-hosted | source verified 2026-10-21 |
| WireMock | open-source | self-hosted, cloud | source verified 2026-10-21 |
About the test class
Chaos and resilience tests: catches retry storms, thundering herds, health-check gaps, rollback failures; cannot catch functional defects, data correctness.
Questions
What is a Chaos and resilience tests tool?
A tool whose own documentation describes chaos and resilience tests: injected failures (dependency down, latency, restart) to check degradation and recovery.
What tools are used for Chaos and resilience tests?
AWS Fault Injection Service, Chaos Mesh, Chaos Toolkit, Grafana k6, Gremlin, Hoverfly, kube-monkey, LitmusChaos, Pumba, Toxiproxy and WireMock, listed alphabetically from their own documentation.
Which Chaos and resilience tests tools are open source?
9 tools are recorded as open source: Chaos Mesh, Chaos Toolkit, Grafana k6, Hoverfly, kube-monkey, LitmusChaos, Pumba, Toxiproxy and WireMock.
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.