← Back to use cases
Test Android Apps on Multiple Device Profiles From One Phone
Build a repeatable profile matrix on one real phone. This page covers profile-based scenarios; use the physical device matrix for real OS, firmware, and hardware differences.
Build a profile matrix
- Save an unchanged baseline profile and record the real phone and Android version.
- Add only the profiles required by your test goals, with complete and internally consistent values.
- Assign one short scenario to each profile and keep the app build, account state, and inputs unchanged.
- Record the profile, changed fields, expected result, actual result, and evidence for every run.
Example matrix
| Run | Changed value | Purpose |
|---|---|---|
| Baseline | None | Confirm the starting scenario |
| Second model | Model and matching build fields | Check model-dependent app logic |
| New identifiers | Android ID and related identifiers | Check account and identifier behavior |
| Network profile | Network and location context | Check context-dependent flows |
When one real phone is not enough
Move to physical devices, emulators, or a device farm for real OS versions, firmware, WebView, camera, sensors, and OEM behavior. Keep those results separate from profile checks instead of claiming full device coverage.
Related guides
Apply and verify one profile · Test without a device farm · Debug inconsistent profile results
Profiles are explained on the device simulation page, and Android testing covers the test environment. The software page has the Device Changer downloads. Downloading needs a free account and login, and using Device Changer's features needs a license.