← Back to use cases
How to Test Android Apps: A Practical Checklist
Start with a small repeatable matrix instead of an unstructured list of devices. This page is a first-run checklist; the complete testing guide covers the full development-to-release process.
A practical first test matrix
| Run | Environment | What it proves |
|---|---|---|
| Baseline | Your unchanged real phone and current app build | The scenario works before profile changes |
| Second profile | One different model profile on the same phone | Behavior changes when profile values change |
| OS check | Each real Android version you support | OS APIs and platform behavior remain compatible |
Scenarios to run first
- Launch the app and complete one core user flow, such as onboarding or a test login.
- Repeat a stateful flow, such as saving data, signing out, and signing in again.
- Test one adverse condition, such as offline mode, denied permission, or an interrupted request.
- Repeat the critical flow after changing only the target profile or only the app build.
Pass criteria
Write the expected result before each run. A scenario passes when the app reaches that state without a crash, corrupted data, or an unexplained environment change. Record the app build, device/profile, real OS, actual result, and evidence. “Looks fine” is not a reproducible pass criterion.
After the first run
Turn repeated scenarios into a regression set and keep the environments stable. Use the QA workflow templates for smoke and release cycles, the debugging checklist when results differ, and the OS compatibility checklist for platform-specific behavior.