← Back to blog
Android QA Release Validation Checklist
Use this checklist before signing off a build. It focuses on release evidence rather than introductory testing theory; beginners can start with the practical testing checklist.
Release validation checklist
- Identify the build: record the version, commit or release candidate, test accounts, and changed features.
- Run smoke scenarios: launch, onboarding, login, main navigation, and one critical business flow.
- Run affected regression scenarios: cover every changed flow plus the features that depend on it.
- Check the environment matrix: include required real Android versions and the device profiles relevant to your users.
- Verify adverse paths: offline mode, denied permissions, interrupted requests, repeated login, and restored app state.
- Attach evidence: expected and actual results, logs or screenshots, profile name, and real OS for every failure.
Sign-off criteria
Approve the release only when all critical scenarios pass on the required environments, there are no open blockers, and every accepted limitation has an owner and a written reason. A pass on a profile is not a pass on a different real OS or hardware platform; keep those results in separate sections of the report.
When a run fails
Return to the unchanged baseline and change one variable at a time. Use the simulation debugging checklist to isolate profile issues and the OS compatibility checklist for platform failures.