Mobile Test Run Type
Overview
Mobile Test Run Type defines how test scenarios are assigned to multiple mobile devices during execution. This feature enables teams to balance device coverage, test predictability, and operational simplicity based on their testing strategy.
Currently, two execution styles are supported:
- Cross
- Random
Each style serves a different business purpose and should be selected based on the intended testing outcome.
At least 2 mobile devices must be added to the device pool in the plan to use Run Types.
Cross Run Type
Description
Cross Run Type executes each test scenario on every device included in the test plan. This execution style ensures full device coverage by running the same scenario across all selected devices, producing one result per scenario per device. It is best suited for compatibility, regression, and consistency validation across different device models and operating systems.
Behavior
- The same scenario is executed on multiple devices
- Device coverage is guaranteed within the execution
- If a plan contains 10 scenarios and 2 devices, each scenario runs on both devices, then a total of 20 results are generated
When to Use
- Regression testing before release
- Compatibility testing across key devices
- UI and behavior consistency validation
- OS or device-specific defect detection
Random Run Type
Description
Random Run Type executes each test scenario on a single device selected randomly during execution. After a scenario completes, the next scenario may run on a different device, as selection is re-evaluated each time. This execution style produces one result per scenario and is suited for continuous testing, stability validation, and increasing device coverage over time.
Behavior
- Random device selection occurs after each scenario execution
- Each scenario is treated independently
- Previously used devices are still included
- The same device may be selected again, as selection is fully random
- If a plan contains 10 scenarios and 2 devices each scenario runs once on a randomly selected device, then a total of 10 results are generated
Random Execution does not guarantee unique device usage within a single plan.
When to Use
- CI/CD pipelines and continuous testing
- Long-running or recurring test plans
- Stability, resilience, and exploratory testing
- Scenarios where device diversity is preferred over predictability
Important Notes
- Use Cross Execution when you need controlled and repeatable validation across specific devices
- Use Random Execution when you want automatic device diversity with minimal setup and long-term coverage
- Random Execution does not guarantee full device coverage within a single test plan
- Selecting the same device multiple times is expected behavior
- For guaranteed multi-device coverage in a single run, Cross Execution should be used