Your Google Play closed-testing checklist
Use this as a working list when Play Console asks you to run a closed test. Keep one note beside each item: done, blocked, or needs checking. That makes the next action visible.
Before the release
- Work through the setup tasks on the app's Dashboard, including its listing. Google's app setup guide.
- Review App content: privacy information, ads, audience, content rating and access instructions for restricted features. Google's review preparation guide.
- Write a short task list and choose somewhere to collect feedback. These are our planning suggestions.
- Choose how to manage testers. If using a group, follow the Google Group guide.
Publish the test build
- Open Test and release > Testing > Closed testing. Manage the track and create a release.
- Follow the signing setup if prompted. Add the app bundle, release name and notes. Review the release and resolve errors before rollout.
Those steps follow Google's release guide. Then check Publishing overview for changes still waiting to be sent for review. Google's publishing guide.
Testers must opt in; being on the list is not enough. Google's tester eligibility rules. Ask one tester to check the full invitation and install flow before sending it widely.
While people test
Our working checklist:
- Keep private notes of confirmed enrollment dates and any departures.
- Ask people to try a useful task, then explain what happened.
- Match each report to a build and device. Separate bugs from suggestions.
- Retest fixes and keep unresolved issues visible.
- Review any available pre-launch report. For setup and coverage, see Google's report guide.
Before applying
Check eligibility in Play Console, then apply from Dashboard > Apply for production. Google's application steps.
Read your feedback log before writing. Explain real use, real changes and remaining limits. Use the application guide to prepare. Leave any public launch date tentative until you have the required decisions.