If your developer account is a personal account created after November 13, 2023, a closed test is not optional: you need at least 12 testers opted in for 14 days in a row before you can apply for production. (If that rule is new to you, start with the 12 testers, 14 days requirement explained.)
This guide walks through setting up the closed test itself, in the order Play Console expects. Google renames menu items from time to time, so if a label differs slightly in your console, look for the closest match in the same section.
Before you start
Have these ready so you are not blocked halfway through:
- A verified developer account. New personal accounts must finish identity and contact verification, and confirm access to a real Android device through the Play Console mobile app.
- A release build as an Android App Bundle (.aab), signed with your upload key, with a version code higher than any build you uploaded before.
- A privacy policy URL. Play Console asks for it during setup, and most apps need one.
- Basic store listing assets: app name, short and full description, app icon, feature graphic and phone screenshots.
- If the app requires a login, test account credentials that reviewers can use.
Step 1: Create the app in Play Console
On the Home page, click Create app. Enter the app name and default language, choose whether it is an app or a game and whether it is free or paid, and accept the declarations. Think carefully about free versus paid: once an app is published as free, it cannot be changed to paid later.
Step 2: Complete the app setup tasks
The Dashboard lists a group of tasks under setting up your app. Your closed testing release will be reviewed, and incomplete declarations are a common reason a review stalls. Work through each item:
- App access: say whether parts of the app are restricted, and give login details if they are.
- Ads: declare whether the app contains ads.
- Content rating: fill in the questionnaire to get your rating.
- Target audience and content: choose the age groups your app is for.
- Data safety: describe what data you collect and share. Be accurate; this appears on your store listing.
- Other declarations that apply to your app, such as government, financial, health or news features.
- Store listing: category, contact details and the graphics listed above.
Step 3: Open the closed testing track
In the left menu, open Test and release, then Closed testing under Testing. Play Console usually creates a default closed track for you. You can use it, or create a new track if you plan to run separate tests later. Click Manage track to configure it.
Step 4: Choose countries and regions
On the Countries / regions tab, add every country your testers are in. A tester in a country you did not select will see the app as unavailable even after opting in. If you are not sure where your testers will be, select broadly for the test; you can narrow it for production later.
Step 5: Add testers
On the Testers tab you choose who may join. There are two ways to do it, and you can combine them.
Email lists
Create a list, give it a name, and add the Google account email addresses of your testers, either typed in or uploaded as a CSV file. Tick the list so it is attached to this track. Email lists work well when you know every tester personally, but you must edit the list each time someone joins or is replaced.
Google Groups
Enter the email address of a Google Group. Everyone who is a member of the group can opt in. This is easier to manage: people join or leave the group and you never touch the track again. It is also how testing services usually work. For example, TesterBie customers add the group [email protected], which contains the Google accounts of our lab phones.
Feedback channel
Set a feedback URL or email address. It is shown to testers when they join, and the feedback you collect here is exactly what Google asks about when you apply for production.
Step 6: Create your first closed testing release
- Click Create new release on the track.
- If asked, accept Play App Signing. Google keeps the app signing key and you sign uploads with your upload key.
- Upload your .aab file and wait for processing to finish. Fix any errors it reports, such as a reused version code or a target API level below what Google Play currently requires.
- Enter a release name (the version name is filled in by default) and release notes telling testers what to try.
- Click Next, review any warnings, then Save.
Step 7: Send the changes for review
Saving a release does not publish it. Go to Publishing overview, check the list of changes and click Send changes for review. If managed publishing is turned on, the changes wait for you to publish them after approval, so remember to come back and do it.
Review times vary. Some apps are approved within hours, while the first review of a new app can take several days. You can keep finishing other setup tasks in the meantime.
Step 8: Share the opt-in link
Once the release is live on the track, the Testers tab shows a link to join the test. On the web it looks like https://play.google.com/apps/testing/your.package.name. Each tester should:
- Open the link while signed in with the same Google account that is on your list or in your group.
- Tap Become a tester to opt in.
- Follow the link to Google Play and install the app, making sure the Play Store on their phone uses that same account.
- Keep the app installed and use it during the test.
From the moment 12 testers have opted in, the 14-day count starts. You can follow it on the Dashboard, where the production access checklist shows the opted-in tester count and the days completed.
Troubleshooting: testers cannot find or install the app
| Symptom | Likely cause | Fix |
|---|---|---|
| The opt-in page says the app is not available | The release is still in review or not yet published | Check Publishing overview; publish the changes if managed publishing is on |
| Tester opted in but the Play Store says 'item not found' | The phone's Play Store uses a different Google account | Switch accounts in the Play Store, or add the other account to the list |
| App shows as unavailable in their country | The country is not selected on the track | Add it under Countries / regions |
| 'Your device isn't compatible' | minSdk, required features or screen support exclude the phone | Check the device catalog in Play Console and your manifest |
| Tester joined the Google Group but cannot opt in | They joined with another account, or the group is not attached to the track | Confirm the membership email and the group on the Testers tab |
Changes to tester lists and newly published releases can take a little while to reach testers. If everything looks right, give it some time before changing settings again.
During the 14 days
A closed test that passes review is one where testers actually used the app and you visibly acted on what they found. While the test runs:
- Check the opted-in tester count every few days and replace anyone who leaves before you drop below 12.
- Watch Android vitals and the pre-launch report for crashes and ANRs.
- Ship at least one update to the closed track that fixes something testers reported, with clear release notes.
- Keep short notes of feedback and changes. You will need them for the production access questions.
Not sure whether a closed track is even the right one for what you are doing? See internal vs closed vs open testing. And when the 14 days are up, read how to answer the production access questions before you click apply.
Finding 12 people who stay opted in for two weeks is usually the hard part, not the setup. If you want to skip that, TesterBie's real Android phones join through our Google Group and use your app daily; see plans and prices.
Frequently asked questions
How many testers can I add to a closed test?
Closed tests are built for invited testers through email lists and Google Groups, and can hold far more people than the 12 the requirement asks for. Recruiting a few extra testers is a good idea so the count never drops below 12.
How long does the closed testing review take?
It varies. Updates to an existing app are often reviewed within hours, while the first review of a new app can take several days. The 14-day count only starts once the release is live and 12 testers have opted in.
Can testers join with any Google account?
No. They must opt in with a Google account that is on one of your email lists or is a member of a Google Group attached to the track, and the Play Store on their phone must use that same account to install the app.
Do I need to give a testing service access to my Play Console?
No. A legitimate service only needs your opt-in link and, if you use one, the Google Group you add to the track. Never share your Play Console password or add an unknown person as an account user.