How to set up closed testing in Play Console, step by step

Most 14-day runs that fail were set up wrong on day zero. The track was internal instead of closed, the release was never rolled out, or the opt-in link was never actually shared. This walks through the setup that works.

Before you start

You need a signed release build (an .aab file), a completed app content declaration, and a store listing with at least the required assets. Play Console will not let you roll out a closed release until the content declarations are green.

1. Create the closed testing track

In Play Console, open your app and go to Testing → Closed testing. Google gives you a default track called Alpha. You can use it or create a new track. Either satisfies the requirement. What matters is that it is a closed track, not internal.

This is the single most common mistake. Internal testing does not count toward the 12 testers requirement no matter how many people you add or how long they stay.

2. Create your tester list

Inside the track, open the Testers tab. You have two options:

• Email list: you paste in Gmail addresses. Precise, and you can see exactly who is on the list.
• Google Groups: you point the track at a group address. Easier to manage at scale.

An email list is the better choice for a first run. You can count the addresses, which means you can prove to yourself you are above 12.

3. Upload and roll out the release

Go to the Releases tab of the track, create a release, upload your .aab, add release notes, and click through to Start rollout to Closed testing. Saving a draft is not enough. If the release is not rolled out, testers who click your link will see nothing to install.

Google reviews the first closed release. This usually takes a few hours but can run to a couple of days. The 14 days do not start until testers can actually install.

4. Copy the opt-in link

On the track page, under the tester list, Play Console shows a Copy link option. That URL, which looks like play.google.com/apps/testing/your.package.name, is what testers open to join. Anyone on your tester list who opens it can accept the invitation and install from the Play Store.

5. Get 12 testers opted in, and keep them there

Opting in is a deliberate act. Being on the email list is not the same as being a tester. Each person must open the link, accept, and install. Play Console's tester count reflects opt-ins, and that is the number Google checks.

Your 14 days are counted from the moment the twelfth tester opts in. Not from when you created the track, not from when you uploaded the build. If your count drops below 12 at any point, the clock restarts.

6. Leave it alone for 14 days

Do not remove testers, do not halt the rollout, do not unpublish the release. You can ship updates to the closed track during the period, which is normal and does not reset anything, but the track must stay live and the tester count must stay at or above 12 every single day.

7. Apply for production access

On day 14, the Play Console dashboard surfaces the production access application. It asks how you recruited testers, what feedback you received and what you changed. Answer it specifically. Vague answers are the second most common cause of refusal after tester drop-off.

The setup checklist

• Track is closed, not internal
• Release is rolled out, not saved as draft
• Tester list has comfortably more than 12 addresses
• Opt-in link has been shared and accepted
• Play Console shows 12 or more testers opted in
• Nothing is touched for 14 continuous days