Mobile Testing
Real device testing
Also known as: on-device testing, physical device testing
Real device testing runs mobile tests on physical hardware rather than on an emulator or simulator, catching the class of defects that only appear with real sensors, real GPUs, real networks and real thermal behaviour.
Emulators and simulators are fast, cheap and reproducible, which makes them the right default for the bulk of a suite. What they do not reproduce is hardware-dependent behaviour: camera and biometric sensors, GPU driver differences, genuine network variability, battery and thermal throttling, and manufacturer OS customisations. Defects in that class are invisible until the test runs on the device itself.
The two also differ in how they flake. An emulator on a contended CI runner flakes from resource starvation — a symptom of the host, not the app. A physical device flakes from state left behind by the previous run, from a system dialog, or from throttling. Both are real, and telling them apart is much easier when results carry the device and OS version as metadata rather than being pooled into one pass rate.
- Emulators are the right default; real hardware catches sensor, GPU, network and thermal defects.
- Emulator flakiness usually indicates host contention, not an app bug.
- Tag results with device and OS version, or the two failure classes are indistinguishable.
Learn more
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