Tools whose documentation names migration tests
8 tools in the catalogue have a documentation page describing migration tests (migrations run against a production-shaped copy with timing and rollback checks). Licences: freemium 2, open-source 5, source-available 1.
Tools, alphabetical
| Tool | Licence | Hosting | Documentation page |
|---|---|---|---|
| Atlas | freemium | self-hosted, cloud | source verified 2026-10-21 |
| Bytebase | open-source | self-hosted, cloud | source verified 2026-10-21 |
| gh-ost | open-source | self-hosted | source verified 2026-10-21 |
| Liquibase | source-available | self-hosted | source verified 2026-10-21 |
| pt-online-schema-change (Percona Toolkit) | open-source | self-hosted | source verified 2026-10-21 |
| Redgate Flyway | open-source | self-hosted | source verified 2026-10-21 |
| Skeema | freemium | self-hosted | source verified 2026-10-21 |
| Sqitch | open-source | self-hosted | source verified 2026-10-21 |
About the test class
Migration tests: catches failing or slow migrations, missing indexes, locks, irreversible changes; cannot catch application code paths that read the new schema.
Questions
What is a Migration tests tool?
A tool whose own documentation describes migration tests: migrations run against a production-shaped copy with timing and rollback checks.
What tools are used for Migration tests?
Atlas, Bytebase, gh-ost, Liquibase, pt-online-schema-change (Percona Toolkit), Redgate Flyway, Skeema and Sqitch, listed alphabetically from their own documentation.
Which Migration tests tools are open source?
5 tools are recorded as open source: Bytebase, gh-ost, pt-online-schema-change (Percona Toolkit), Redgate Flyway and Sqitch.
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.