Tools whose documentation names integration tests
5 tools in the catalogue have a documentation page describing integration tests (real dependencies (database, queue, provider sandbox) exercised together). Licences: open-source 4, freemium 1.
Tools, alphabetical
| Tool | Licence | Hosting | Documentation page |
|---|---|---|---|
| Hoverfly | open-source | self-hosted | source verified 2026-10-21 |
| Postman | freemium | cloud, self-hosted | source verified 2026-10-21 |
| Serenity BDD | open-source | self-hosted | source verified 2026-10-21 |
| Testcontainers | open-source | self-hosted, cloud | source verified 2026-10-21 |
| TestNG | open-source | self-hosted | source verified 2026-10-21 |
About the test class
Integration tests: catches ORM semantics, webhook handling, connection handling, SDK behaviour; cannot catch production data volume, prod-only config, network conditions.
Questions
What is a Integration tests tool?
A tool whose own documentation describes integration tests: real dependencies (database, queue, provider sandbox) exercised together.
What tools are used for Integration tests?
Hoverfly, Postman, Serenity BDD, Testcontainers and TestNG, listed alphabetically from their own documentation.
Which Integration tests tools are open source?
4 tools are recorded as open source: Hoverfly, Serenity BDD, Testcontainers and TestNG.
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.