Compatibility tests: what they catch and the release incidents they cover
Compatibility tests (the same flow across browsers, OS versions and device classes) run at the pre-deploy stage.
2 published incident types list compatibility tests as a class that catches them; 0 of these links are cited in a public report and 2 are by design analysis.
What compatibility tests catch and cannot catch
Catches
- crashes on older OS
- single-browser failures
- hydration faults
Cannot catch
- server-side faults
- load
Both lists come from the site's test class definitions.
Incident types this class catches
| Incident | Stage | Limitation on that page | Basis |
|---|---|---|---|
| Crash on older OS version | pre-deploy | A compatibility run on a binary from a different build passes, because one reported crash came from the build tooling rather than from app code. | by design analysis |
| Critical path broken in one browser | pre-deploy | A compatibility run on the current iOS browser passes, because the unsupported regular expression broke only versions below 16.4. | by design analysis |
For cited rows the number shows how many reports on that incident page name this class.
Only on this page
No public report on a published incident page names compatibility tests explicitly; every link on this page is by design analysis. The incident with the most public reports that lists this class is Crash on older OS version.
Catalogue entries that name this class
From their own documentation or site, with the verification date. Alphabetical. Not a recommendation.
Tools whose documentation names these test classes
- Applitools Eyes compatibility source verified 2026-10-21
- BrowserStack compatibility source verified 2026-10-21
- CodeceptJS compatibility source verified 2026-10-21
- Cypress compatibility source verified 2026-10-21
- Datadog Synthetic Monitoring compatibility source verified 2026-10-21
- Firebase Test Lab compatibility source verified 2026-10-21
- Karate compatibility source verified 2026-10-21
- Katalon Studio compatibility source verified 2026-10-21
- Kobiton compatibility source verified 2026-10-21
- Nightwatch compatibility source verified 2026-10-21
- Playwright compatibility source verified 2026-10-21
- Robot Framework compatibility source verified 2026-10-21
- Sauce Labs compatibility source verified 2026-10-21
- Selenium compatibility source verified 2026-10-21
- Serenity BDD compatibility source verified 2026-10-21
- TestCafe compatibility source verified 2026-10-21
- TestingBot compatibility source verified 2026-10-21
- TestMu AI (formerly LambdaTest) compatibility source verified 2026-10-21
- Vitest compatibility source verified 2026-10-21
- WebdriverIO compatibility source verified 2026-10-21
Providers whose site names these test classes
- Abstracta compatibility source verified 2026-10-21
- Appmatics compatibility source verified 2026-10-21
- BugRaptors compatibility source verified 2026-10-21
- Crestech Software Systems compatibility source verified 2026-10-21
- DeviQA compatibility source verified 2026-10-21
- Elinext compatibility source verified 2026-10-21
- Full Scale compatibility source verified 2026-10-21
- Inmetrics compatibility source verified 2026-10-21
- iScale Solutions compatibility source verified 2026-10-21
- Nimble Approach compatibility source verified 2026-10-21
- Outpost QA compatibility source verified 2026-10-21
- Polteq compatibility source verified 2026-10-21
- Q-Centric GmbH compatibility source verified 2026-10-21
- QA Madness compatibility source verified 2026-10-21
- QA Mentor compatibility source verified 2026-10-21
- QASource compatibility source verified 2026-10-21
- QAwerk compatibility source verified 2026-10-21
- QualityKiosk Technologies compatibility source verified 2026-10-21
- SimplyTest GmbH compatibility source verified 2026-10-21
- Sofka Technologies compatibility source verified 2026-10-21
- Soflab Technology compatibility source verified 2026-10-21
- SQA - Software Quality Assurance S.A. compatibility source verified 2026-10-21
- SunTec India compatibility source verified 2026-10-21
- TestFort compatibility source verified 2026-10-21
- Testhouse compatibility source verified 2026-10-21
- Testing IT compatibility source verified 2026-10-21
- TestMatick compatibility source verified 2026-10-21
- Testrig Technologies compatibility source verified 2026-10-21
- Testscenario compatibility source verified 2026-10-21
- VTEST compatibility source verified 2026-10-21
- WebDepend compatibility source verified 2026-10-21
Questions
What is Compatibility tests?
Compatibility tests: the same flow across browsers, OS versions and device classes. They run at the pre-deploy stage.
What does Compatibility tests catch?
Compatibility tests catch crashes on older OS, single-browser failures and hydration faults. 2 published incident types list this class.
What can Compatibility tests not catch?
Compatibility tests cannot catch server-side faults and load.
How is Compatibility tests different from other test classes?
Compatibility tests share the pre-deploy stage with contract tests, integration tests, end-to-end tests, migration tests, load and performance tests, security tests, configuration and environment tests and chaos and resilience tests; they differ in what each catches.
Can Compatibility tests run in a production environment?
Compatibility tests run at the pre-deploy stage, before production traffic.
Which incidents is Compatibility tests used for?
crash on older OS version and critical path broken in one browser. 0 of 2 links are cited in a public report; the rest are by design analysis.