Cloud device testing, also called remote device testing or a device cloud, is running tests on real mobile devices hosted by a service provider and accessed over the internet. It sits between emulators and an in-house device lab.
Why it matters: It gives access to far more real devices than most teams can buy and maintain, which helps with device fragmentation while still testing on real hardware rather than emulators.
In practice: Teams connect to the provider's devices through a browser or their test automation tools, running manual sessions or automated suites. It's often used later in testing, once early functional bugs have been found on emulators, and for reproducing problems on specific models customers use.
Examples:
- Running a regression suite on twenty remote devices before a release.
- Reproducing a customer's bug on a remotely hosted copy of their exact phone model.
Common pitfalls:
- Assuming remote devices reflect real-world networks, when they usually sit on fast, stable connections.
- Forgetting security and data handling when test data passes through a third-party service.
Is cloud device testing the same as using emulators? No. Cloud device testing uses real physical devices, hosted remotely. Emulators are software imitations running on a computer.
