← Back to use cases
Android Device Simulation Debugging
Use this checklist when a scenario passes on one profile and fails on another. The goal is to isolate the cause instead of changing several settings until the original bug becomes impossible to reproduce.
Change one variable at a time
- Return to the baseline profile and confirm that the original result still occurs.
- Apply the target profile without changing identifiers, network settings, or app data.
- Repeat the same scenario with identical account state and inputs.
- If the result changes, alter only one additional value in the next run and record it.
Capture evidence
For every run, save the app build, profile name, real Android version, changed value, expected result, actual result, and relevant log excerpt. Add a screenshot when the failure is visual. A useful record lets another developer reproduce the issue without guessing which random values were active.
Compare and classify the failure
- Baseline also fails: investigate the app scenario, test data, or module setup before changing profiles.
- Only the target profile fails: inspect the values that differ and the app code that reads them.
- Only one real Android release fails: test OS behavior separately; a profile does not turn the phone into that release.
- Result changes between identical runs: check network state, cached app data, and background services before accepting the result.
Related guides
Apply and verify one profile · Reproduce mobile app bugs · Build a QA profile matrix
For the wider picture, QA testing shows how profile checks fit a full QA process, and Android testing covers the environment these profiles run in.