Closed Testing
The Android Test Runbook: Preparation, Investigation, Handoff
Build a practical operating plan for a private Android test from the first brief to the final decision.
On this page · 4 sections
At a glance
In plain English
- Prepare an executable brief
- Operate a daily investigation queue
- Hand over a decision record
Prepare an executable brief
Write the app's purpose, supported devices, install instructions, test accounts, and reporting route in one place. Select the journeys where failure would matter most. Verify the brief with one person outside the development team and correct anything they cannot follow without assistance.
Operate a daily investigation queue
Review new findings, reproduce actionable failures, and assign owners. Keep a build identifier on every report. Send corrected journeys back for confirmation while maintaining a separate view of participation eligibility. A quiet issue queue can mean unclear instructions, so ask whether participants know what to report.
Hand over a decision record
Summarise covered journeys, changed behaviour, verified fixes, and remaining limitations. Include who will handle post-release issues. Use the official Play Console workflow for eligibility and production access; a runbook organises your work but does not confer publishing permission.
Sources
Official references used
- App testing requirements for new personal developer accounts (Google Play Console Help)
- Set up an open, closed, or internal test (Google Play Console Help)
- Release app updates with staged rollouts (Google Play Console Help)
- Prepare and roll out a release (Google Play Console Help)
Continue
Choose the next step
Related
Next pages to read
Need 12 testers for 14 days?
Start a managed Google Play closed-testing run with verified testers, opt-in monitoring, and a closeout report.