Mobile Testing
Device fragmentation
Also known as: OS fragmentation, device matrix spread
Device fragmentation is the spread of hardware models, screen sizes, OS versions and vendor customisations a mobile app must run on — the reason a mobile test matrix is combinatorial rather than a single environment.
A web suite typically targets a handful of browser engines. A mobile suite faces a far larger cross-product: Android spans many API levels, manufacturer skins and screen densities simultaneously, while iOS concentrates on fewer devices but still spans several OS versions in active use. Every additional axis multiplies the matrix rather than adding to it, so exhaustive coverage is never the goal — representative coverage is.
Fragmentation is also a flakiness source, not just a coverage cost. The same test can pass on one API level and fail on another because of animation timing, permission-dialog behaviour, or a vendor-specific WebView. That is why mobile results are worth analysing per device and per OS version rather than as one aggregate pass rate: an 97% pass rate hiding a single consistently-failing OS version is a different problem from one spread evenly.
- The matrix is combinatorial — each axis multiplies, so pick representative devices, not all of them.
- Fragmentation causes flakiness as well as coverage gaps.
- Aggregate pass rate hides device-specific failure; segment results by device and OS version.
Related terms
See it in your own test results
Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.
Start free with Qualflare← Back to the testing & observability glossary.
Last reviewed September 10, 2026