Running mobile tests
Mobile tests run the same way as web tests. Each run executes the generated script on a cloud-hosted device in a fresh, isolated session.
Triggering runs
Section titled “Triggering runs”- Manually from the UI, as an individual test or as part of a collection.
- On a schedule, set in the collection details.
See Running tests and Collections.
Devices
Section titled “Devices”Runs execute on real devices and emulators. The device a run used is shown in the run details.
You can also pick a specific device and OS version in the run settings of a collection, see Run settings. The chosen device is then shown under Run settings.
Browser engine and viewport settings do not apply to mobile tests.
Run settings
Section titled “Run settings”By default each test runs with its own settings. To change how a whole collection runs, click Configure under Run settings on the collection page.
| Setting | Value |
|---|---|
| Locale | The locale to run with |
| Device | A specific device name and OS version, e.g. Pixel 9 and 15 |
| Mobile app override | Run the tests against a different app build, see App builds |
| Override variables | Temporary values for variables, see Parameters in runs |
Click Save to apply the settings, or Clear to go back to each test’s own settings.
Running against a different build
Section titled “Running against a different build”To check a new version of your app with existing tests, upload the build and select it under Mobile app override.
Healing and notifications
Section titled “Healing and notifications”These work as they do for web tests:
- Self healing when the app changes
- Notifications for failed runs
If your app uses backends that are not on the public internet, see Tunneling options.