Tools whose documentation names contract tests
3 tools in the catalogue have a documentation page describing contract tests (consumer and provider agree on request and response shape before deploy). Licences: open-source 3.
Tools, alphabetical
| Tool | Licence | Hosting | Documentation page |
|---|---|---|---|
| Pact | open-source | self-hosted | source verified 2026-10-21 |
| Schemathesis | open-source | self-hosted | source verified 2026-10-21 |
| Specmatic | open-source | self-hosted | source verified 2026-10-21 |
About the test class
Contract tests: catches schema drift between services, provider API field changes, dropped API versions; cannot catch runtime data values, performance, auth policy.
Questions
What is a Contract tests tool?
A tool whose own documentation describes contract tests: consumer and provider agree on request and response shape before deploy.
What tools are used for Contract tests?
Pact, Schemathesis and Specmatic, listed alphabetically from their own documentation.
Which Contract tests tools are open source?
3 tools are recorded as open source: Pact, Schemathesis and Specmatic.
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.