Google Play closed testing guide
Go from a closed testing release in Play Console to an application for production access. Track how people use your app and record the changes you make from their feedback.
Applies to personal developer accounts created after November 13, 2023.
Google Play requirements
When you apply for production access, at least 12 testers must still be opted in to your closed test and must have remained opted in for the preceding 14 consecutive days.
Each tester opts in through the Google Play link. If they leave the test and opt in again, their continuous period starts over.
Set up your closed test
Create a closed testing release
Select your app in Play Console. Under Test and release → Testing → Closed testing, complete your app setup and add your Android App Bundle (.aab) to a release for that track.
Give testers access
Add their Google Account email addresses to your tester list or use a Google Group. If you use a group, testers must join it before they opt in.
Share the opt-in link
Once the test release is published, copy the link from the Testers tab. Ask testers to use the invited Google account, opt in and install your app from Google Play.
Run the test and gather feedback
Recruit people who match your target audience and test on relevant devices and Android versions. Give them tasks that reflect actual app use, such as signing up, completing a core workflow, retrying without a connection or updating to a newer build.
Choose a feedback channel such as Google Play private testing feedback, email or a form. For each issue, record the build, device, reproduction steps, observed result and any changes you made. Retest fixes on the updated build.
Record usage and feedback that you actually observed. If a feature went untested or you received limited feedback, note it so that you can investigate it further.
Apply for production access
When Apply for production is available in the Play Console dashboard, submit your application. Prepare the three sections using information from your own test.
Your closed test
Who did you recruit, how difficult was recruitment, and which features did testers use? Did their usage resemble expected production use? How did you collect feedback, and what did it tell you?
Your app or game
Who specifically is it for? What problem does the app solve or what is distinctive about the game? Estimate first-year installs based on your own plans.
Readiness for release
What changed in response to feedback? Record the build versions, fixes or retesting that helped you decide the app was ready.
Google reviews your application for Production track access. After access is granted, you still prepare a production release and follow the review and rollout steps shown in Play Console.
If Google asks for more testing
If Google asks for further testing, read the Play Console notice, keep the closed track active and address the feedback you received. Reapply once you meet Google’s instructions and have new findings to report.
For eligible Zovatesting requests, our team can manually coordinate up to three additional testing rounds for the same package name. Use the app’s Reports section to describe Google’s feedback and include a link to the notice when available.
Developers resolve release-blocking issues and upload a new build when the app needs changes. We confirm scope for each eligible request. Google decides production access and release review outcomes.