Adding 12 testers to a closed testing track in Google Play Console takes about 5 minutes once you have the tester emails. This guide walks through every click, the exact opt-in URL format, and how to verify your testers actually opted in.
Before you start
Make sure you have:
- A Google Play Console account with the app already created.
- An APK or Android App Bundle ready to upload.
- 12 tester email addresses (Gmail or any Google account email).
Need Testers?
If you don't have 12 reliable testers yet, you can order them from us — we deliver verified accounts in 2–6 hours.
Create the closed testing track
- Sign in to Google Play Console.
- Select your app from the app list.
- In the left sidebar, click Testing → Closed testing.
- Click the Create track button at the top.
- Name your track (e.g. "Closed Test" or "12 Testers — 14 Days").
- Click Create track to confirm.
You'll land on the track's overview page with three tabs: Releases, Testers, and Settings.
Upload your build
- Click the Releases tab.
- Click Create new release.
- Follow the prompts to upload your APK or AAB. You'll need to sign it with your upload key (the same one used for your production builds).
- Add a release name (e.g. "1.0.0-closedtest") and release notes.
- Click Review release → Start rollout to Closed testing.
Google will review the build (usually takes 5–30 minutes for a closed track). Once approved, the build is available to opted-in testers.
Add tester email addresses
- Click the Testers tab.
- Click Create email list.
- Name the list (e.g. "12 Real Testers").
- Paste your 12 tester email addresses, one per line.
- Click Save.
You can have multiple lists (e.g. one for the 14-day test, one for internal QA). For the 12-tester requirement, one list is enough.
Share the opt-in URL
- On the Testers tab, look for the Opt-in URL field.
- Click the copy icon next to the URL.
- Send the URL to your 12 testers via email, Slack, or any channel.
When testers open the URL on their Android device, they'll see your app's Play Store listing with a Become a tester button. They must tap it to opt in.
Verify your testers opted in
- Go back to the Testers tab in Play Console.
- Look at the Testers count — this shows how many have actually opted in.
- For a detailed list, click the email list name. You'll see each tester's email and their opt-in status.
Wait until you see all 12 testers listed as opted in. Once you have 12, the 14-day continuous test window begins.
Start the 14-day clock
The 14-day window starts automatically once you have 12 opted-in testers. You don't need to do anything else. Just make sure:
- Your build remains available (don't unpublish or pause the track).
- Your testers can install and use the app.
- You don't reset the testers list.
Common mistakes to avoid
Adding emails but not sharing the URL
Many developers add tester emails to the console and assume that's enough. It's not — testers must click the opt-in URL and tap "Become a tester." If they don't, Google won't count them.
Resetting the tester list
If you remove and re-add testers mid-test, the 14-day clock may reset. Only add new testers if you need to top up.
Pausing the track
If you pause the closed testing track (e.g. to fix a build issue), the 14-day window pauses. The clock resumes when you unpause — but if the pause is too long, the milestone may not count.
Same Google account for multiple testers
Google counts unique Google accounts, not email aliases. If 12 of your "testers" all use the same underlying Google account or device, it counts as 1. Each tester needs their own unique Google account.
After 14 days
Once the 14-day window is complete:
- Go to your app's Dashboard in Play Console.
- Confirm the "Closed testing" milestone is marked complete.
- You can now apply for production access. Go to Release → Production and create a production release.
Google reviews production access applications in 1–7 days. Once approved, your app is live on the Play Store.