Tips for Achieving Device Coverage in Waldo

Ensuring a consistent, bug free experience for every end user requires thorough testing that accounts for multiple devices, OSs, and languages.

📘

Limit your setup

If you are doing this manually or maintaining your own simulated devices, this can require hours of device cleanup and maintenance work.

That is why one of the core motivators for mobile testing automation is scaling your device coverage.

Waldo provides a clean simulator or emulator device with the OS, and language of your choosing for every test run…even for real time interactions in Waldo Live.

Our multi-concurrency testing model allows you to test multiple devices with different languages and operating systems simultaneously: reducing the amount of time it takes to run your test while achieving total coverage.

Best practices for achieving device coverage in Waldo

📘

Work smarter, not harder

While you can select multiple device types with every test run in Waldo, it is important to be strategic about how many devices a test is being run on to ensure optimal coverage + easier test maintenance.

Let’s say you want to make sure you support the 2 latest iPhones, with the last 2 iOS versions, and your app is available in English and French.

Instead of testing on 12 configurations :

iPhone 13 - 15.4.0 - EN
iPhone 13 - 15.4.0 - FR
iPhone 13 - 15.3.0 - EN
iPhone 13 - 15.3.0 - FR
iPhone 14 - 15.4.0 - EN
iPhone 14 - 15.4.0 - FR
iPhone 14 - 15.3.0 - EN
iPhone 14 - 15.3.0 - FR

You get roughly the same coverage for testing only those 2 configurations :
iPhone 13 - 15.4.0 - EN
iPhone 14 - 15.3.0 - FR

AND this will allow you to maintain the fastest possible testing time without compromising on your device coverage.

This ensures that your test:

Is easier to maintain
If/When updates are required for your test, you don’t need to update 12 different baselines for 12 device configurations, or worry about a test failing on multiple devices when an update does not work on later configurations.

Provides a faster path to results
If you choose to run tests using a single concurrency, you can condense test time by limiting the number of devices the test has to be run on.