How to Set Up a Google Play Closed Test (Step by Step)

A closed test lets a specific list of people install your app from Google Play before it's public. For new personal developer accounts it's also mandatory: you need 12 testers opted in for 14 days before production access. Here's how to set one up correctly the first time, based on Google's open, closed and internal testing help page.

Before you start

• A signed release build (an Android App Bundle, .aab) with a unique applicationId, e.g. com.yourstudio.app.
• Your store listing basics filled in (app name, short description, icon, screenshots) and the App content questionnaires completed. Play Console lists anything missing on the dashboard. See our App content checklist.
• A plan for who your testers are. If you use TestersZone, you'll receive their Google account emails as they join.

Step 1: Create the closed testing track

1. In Play Console, open your app and go to Test and release → Testing → Closed testing.
2. Use the default closed track or create a new one, then select Manage track.
3. Create a new release, upload your .aab, add release notes and save.
4. Send the changes for review. Testers can only get the app once the release is available on the track.

Step 2: Email lists vs Google Groups

On the track's Testers tab you choose how testers get access:

Both work for the 14-day requirement. What matters is that each tester opts in with the same Google account they use in the Play Store on their phone.

Step 3: Find and share your opt-in link

Still on the Testers tab, scroll to How testers join your test and copy the link. It usually looks like https://play.google.com/apps/testing/com.yourstudio.app. Google notes that this link only displays when the app's status is published on the track, so if you can't see it, check that your release has gone live for testing.

When a tester opens the link, they see an explanation and a Become a tester button, then a link to install the app from Google Play.

Step 4: Add TestersZone testers in under a minute

1. When you list your app, paste the opt-in link and your package name.
2. As testers join, open your app in the dashboard → Testers tab → Copy tester emails.
3. Paste them into your Play Console email list and save. New testers can then open the opt-in link and install.
4. Once you see them in Play Console, click Mark verified on TestersZone so everyone knows they're counted.
5. When 12+ have opted in, click Start 14-day clock to track progress.

Optional but recommended: set an in-app verification code (for example on your About screen). Testers must type it to check in, which proves they opened your app. Learn more on the verification page.

Common setup mistakes

• Using internal testing. Internal test tracks don't satisfy the closed-testing requirement. See internal vs closed vs open testing.
• Forgetting to save the email list after pasting addresses, or adding the list to a different track.
• Testers opting in with the wrong account. Ask testers to use the account signed into their phone's Play Store. TestersZone asks for this email when they join.
• Countries / devices excluded. If your release targets only some countries or devices, some testers may not be able to install.
• Pausing the track. Keep the closed track active for the whole 14 days and until production approval.

Testers still can't get in? See 7 fixes for closed test opt-in problems. Next up: keeping testers engaged for all 14 days.