How to set up closed testing in Google Play Console, step by step
Create the closed testing track, add testers, upload your app bundle, get the opt-in link and start counting the 14 days, without the usual mistakes.
Updated 20 Nov 2026
Before you start
You need a Google Play developer account, a signed Android App Bundle (.aab) and a privacy policy URL. Play Console menus change from time to time, so the names below may differ slightly, but the order of the steps stays the same.
Plan for review time. A closed testing release goes through Google’s review, which can take from a few hours to several days for a new app. The 14 days only start for each tester after they opt in, so the sooner the release is approved, the sooner you can apply for production.
1. Create the app and finish the setup tasks
Create the app from the Play Console home page: name, default language, app or game, free or paid. Then open the Dashboard and complete the “Set up your app” tasks.
These include the privacy policy, app access (give Google a test login if your app needs one), ads, content rating, target audience, data safety and the main store listing with icon, feature graphic and screenshots. A closed test cannot go to review while required tasks are missing.
2. Open the closed testing track
Go to Test and release, then Testing, then Closed testing. Play Console creates a default closed track; you can use it or create a new one. One track is enough for the 12 testers requirement.
3. Choose countries and testers
In the Countries / regions tab, select every country where your testers live. A tester in a country you did not select will not be able to install the app.
In the Testers tab, create an email list and paste each tester’s Google account: on TesterTribe you find them in My tribe, ready to copy. Play Console also accepts Google Groups, but they can show every member’s email to the others; our guide on Google Group or email list explains why we use lists. Add a feedback email or URL: testers see it on the opt-in page.
4. Upload a release and roll it out
Create a new release in the closed track:
- Upload your signed app bundle. Play App Signing is set up the first time.
- Give the release a name and write release notes that tell testers what to try.
- Save, review the release and fix any errors Play Console shows.
- Roll out the release to closed testing.
5. Send the changes for review
Open Publishing overview and send the changes for review. If managed publishing is off, changes go to review automatically. You get an email when the release is approved.
6. Share the opt-in link
When the release is available, the Testers tab shows the opt-in link, in the form play.google.com/apps/testing/ followed by your package name. Share it with your testers. They open it while signed in with the invited Google account, accept, and then install the app from Google Play.
If the link shows an error, read our guide on the opt-in link not working: it is almost always the wrong Google account, a country not selected or a release still in review.
7. Keep 12 testers for 14 days, then apply
From now on, each tester counts from the moment they opt in. Keep at least 12 of them in the test for 14 days in a row, ship an update during the test and collect feedback. Then apply for production access from the dashboard.
On TesterTribe your campaign gets 12 testers plus 2 reserves, and the 14 days start for everyone together when you confirm in Play Console that 12 testers are in.
Frequently asked questions
How long does the closed testing review take?
For a new app it can take from a few hours to several days. Google sends an email when the release is available to testers.
Do I need a privacy policy for a closed test?
Yes. The privacy policy is one of the setup tasks Play Console asks for before your app can go to review.
Can I update the app during the closed test?
Yes. Uploading new releases to the same track does not reset the 14 days, and an update based on feedback is good evidence for your production access application.