Testing and release-safety tools: documented facts
The catalogue lists 89 tools whose own documentation names at least one of the site's test classes. Public examples only. Tools and providers listed by what their own documentation says, in alphabetical order, with no ratings.
All tools
89 of 89 entries, alphabetical
- Appium e2e
- Applitools Eyes e2e, compatibility
- Argo Rollouts canary
- Artillery load
- Atlas migration
- AWS Fault Injection Service chaos
- axe-core e2e
- behave e2e
- BrowserStack compatibility
- Burp Suite security
- Bytebase migration
- Chaos Mesh chaos
- Chaos Toolkit chaos
- Checkly synthetic, e2e
- Checkov security
- CodeceptJS e2e, compatibility
- Cucumber e2e
- Cypress e2e, compatibility
- Datadog Synthetic Monitoring synthetic, e2e, compatibility
- Detox e2e
- Drill load
- Espresso e2e
- Firebase Test Lab compatibility, e2e
- Flagger canary
- Flipt config
- Gatling load
- gh-ost migration
- Gitleaks security
- Grafana Cloud Synthetic Monitoring synthetic
- Grafana k6 load, synthetic, chaos
- Gremlin chaos
- GrowthBook config, canary
- hey load
- Hoverfly integration, chaos
- Jest unit
- JUnit unit
- Karate e2e, compatibility, load
- Katalon Studio e2e, compatibility
- Kayenta canary
- Kobiton e2e, compatibility
- kube-monkey chaos
- LaunchDarkly config, canary
- Liquibase migration
- LitmusChaos chaos
- Locust load
- Maestro e2e
- Mocha e2e
- Nightwatch e2e, compatibility, unit
- Nuclei security
- oha load
- Pa11y e2e
- Pact contract
- Percy e2e
- Playwright e2e, compatibility
- PostHog config
- Postman integration, load, synthetic
- pt-online-schema-change (Percona Toolkit) migration
- Pumba chaos
- Puppeteer e2e
- pytest unit
- Redgate Flyway migration
- Robot Framework e2e, compatibility
- RSpec unit, e2e
- Sauce Labs compatibility, e2e
- Schemathesis contract, security
- Selenium e2e, compatibility
- Semgrep security
- Serenity BDD e2e, integration, compatibility
- Skeema migration
- SonarQube security
- Specmatic contract
- Spinnaker canary
- Sqitch migration
- sqlmap security
- TestCafe e2e, compatibility
- Testcontainers integration
- TestingBot compatibility, e2e
- TestMu AI (formerly LambdaTest) compatibility, e2e, load
- TestNG unit, integration
- Toxiproxy chaos
- Trivy security
- TruffleHog security
- Unleash config, canary
- Uptime Kuma synthetic
- Vitest unit, compatibility
- WebdriverIO e2e, compatibility, unit
- WireMock chaos
- XCTest unit, e2e
- Zed Attack Proxy (ZAP) security
Data status
| Page type | Published | Withheld |
|---|---|---|
| Tool pages | 89 | withheld 14 |
| Tools by test class | 12 | withheld 0 |
| Tool comparisons | 32 | withheld 8 |
Questions
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.
How often are tool facts re-verified?
Tool facts older than 12 months are re-verified at each refresh; every fact shows its verification date.