How to set up a closed test in Play Console, step by step

This is the setup Google needs before your fourteen days can start. It takes about half an hour if everything is ready, and most of the delays people hit come from doing the steps out of order.

If you have not checked whether the 12-tester rule applies to your account, do that first. And make sure you are using closed testing: internal testing does not count.

Before you start

You need:

• An app created in Play Console. Settle the package name before you upload: once your first build is uploaded, it is permanent.
• A signed Android App Bundle (.aab) of a build you are happy for strangers to use.
• The setup tasks on the app's Dashboard. Play Console lists what it still needs, such as app access, ads, content rating, target audience and the Data safety form, plus a store listing. Testers see a store page when they install, so a listing has to exist. Finish whatever Play Console marks as required for testing before you create the release.

Step 1: Open closed testing

1. Sign in to Play Console and select your app.
2. Go to Test and release → Testing → Closed testing.
3. Click Manage track on the closed track Play Console already created. You can also click Create track to add a new one, but one track is enough for the requirement.

Step 2: Choose countries and regions

Select where the test is available. A tester in a country you have not selected cannot install the app, which looks exactly like a tester who never opted in.

Google notes that changes to your distributed countries and regions apply across all tracks, so check this before launch.

Step 3: Add testers

Open the Testers tab and choose one of two methods.

Email list

Best when you know each tester's Google account address.

1. Click Create email list and give it a name. Lists can be reused across your apps.
2. Add addresses separated by commas, or upload a CSV file (not UTF-8 with a byte-order mark, which Play Console rejects).
3. Click Save changes, then Create, and tick the list for this track.

Google's limits are generous: up to 200 lists, 2,000 users per list and 50 lists per track.

Most common mistake: adding an address the tester does not use on their phone. If their phone is signed in to a different Google account, they will not be able to join.

Google Group

Best when testers should be able to join by themselves, as in an exchange or a community.

1. Create a group at groups.google.com and allow people to join.
2. In the Testers tab, choose Google Groups and enter the group address, in the form [email protected].

Only members of the group can join the test, so testers join the group first, then use the opt-in link.

Feedback channel

The Testers tab also has a feedback field for an email address or URL. Fill it in. Testers see it, and you will need their feedback for the production access questions.

Step 4: Create and publish the release

1. Click Create new release on the closed track.
2. Upload your .aab and add short release notes.
3. Review the release and roll it out.

Closed testing releases are reviewed by Google before testers can get them. This can be quick or take several days, especially for a new app, so do not promise testers a start date until the release is published.

Step 5: Share the opt-in link

Once the release is published, the Testers tab shows the opt-in link. It is the only link that makes someone count.

When a tester opens it, Google explains what being a tester means and shows a button to join. After joining they install the app from its Play Store page.

• Share the opt-in link, not the store link. Installing without opting in does not count.
• Every tester must opt in themselves. You cannot do it for them.

Step 6: Verify and start counting

Your fourteen days need at least twelve testers opted in the whole time. Do not trust replies saying "done". Check the count in Play Console, and match each tester to the account they joined with. How to verify a tester actually opted in.

Then check the count every two or three days until Google grants production access. Play Console shows the current number, not a history, so a drop you do not see is a drop you cannot fix.

Where the testers come from

The setup is the easy part. Twelve real people who keep your app for two weeks is the hard part. Every free way to get them, ranked by how well each keeps testers opted in.