PlayStore12TesterPlan and record 18 release checks across installation, user journeys, connectivity, accessibility, integrations and evidence. Mark only what you actually tested.
This checklist records your observations. Completion is not a certification or a guarantee of Google Play approval.
- Not checked
- 18
- Passed
- 0
- Failed
- 0
- Not applicable
- 0
01 · Install and update
02 · Core user journeys
03 · Connectivity and lifecycle
04 · Readability and accessibility
05 · App-specific integrations
06 · Evidence and release decision
Android release test checklist
- App name
- Not provided
- App version and build
- Not provided
- Test environment and scope
- Not provided
Not checked: 18 · Passed: 0 · Failed: 0 · Not applicable: 0
Install and update
Fresh install (Not checked)
Install the exact release candidate on a representative device. Confirm the first launch and record the build.
Update from the previous release (Not checked)
Check that an update preserves expected user data and settings. Record both build versions.
Permission choices (Not checked)
Exercise allow, deny and later changes for permissions the app actually requests. Confirm useful explanations and recovery.
Core user journeys
First useful action (Not checked)
Complete the main task from a fresh start. Record steps, test data and the visible outcome.
Sign-in and sign-out (Not checked)
If the app has accounts, check valid and invalid input, expired sessions and sign-out. Use dedicated test accounts.
Input and error recovery (Not checked)
Try empty, long and invalid input in relevant forms. Confirm clear errors and that a retry does not duplicate an action.
Connectivity and lifecycle
Offline and reconnect (Not checked)
Interrupt connectivity during a key flow, then restore it. Check error handling, retries and data consistency.
Background and resume (Not checked)
Leave the app during a key task and return. Check that state is preserved or recovered clearly.
Rotation and window size (Not checked)
Change orientation and supported window sizes. Confirm important actions remain usable and state remains consistent.
Readability and accessibility
Smallest supported screen (Not checked)
Inspect dialogs, keyboard-open forms and primary actions at the smallest supported window size.
Large text and display scaling (Not checked)
Increase font and display size using device settings. Check labels, errors and scrolling without hiding important actions.
TalkBack journey (Not checked)
With TalkBack enabled, check focus order, meaningful labels and completion of the main journey. Record manual observations.
App-specific integrations
Purchases and restore (Not checked)
Where applicable, use the platform test environment to check success, cancellation, pending states and restoring access.
Notifications and deep links (Not checked)
Where applicable, open relevant links and notifications from foreground, background and closed states.
Supported languages and RTL (Not checked)
Check the languages your app supports, long labels, dates and right-to-left layouts where relevant.
Evidence and release decision
Crashes and responsiveness (Not checked)
Repeat the key journeys and review available crash or diagnostic evidence. Record observed freezes or crashes with context.
Fixes and regression checks (Not checked)
Repeat the original failing steps on the fixed build and check adjacent journeys. Keep unresolved items visible.
Scope and known limitations (Not checked)
Record tested devices, builds, excluded areas, unresolved issues and the person responsible for the release decision.
This checklist records your observations. Completion is not a certification or a guarantee of Google Play approval.
How to Test an Android App Before Release
Build an Android release test plan: define scope, choose representative devices, check key journeys and record results before shipping.
FREE TOOLAndroid Bug Report Generator
Create a structured Android bug report with reproduction steps, device details and outcomes. Download Markdown or print to PDF in your browser.