If your personal developer account is new, a closed test with at least 12 testers is the gate between your finished app and production — the rule itself is covered in our 12 testers & 14-day requirement guide. This guide is the practical part: setting the test up in the order Play Console actually needs it, so the 14 days start as soon as possible.
A lot of lost time happens before the clock even starts — a track that never went live, an opt-in link that doesn't work yet, testers added in the wrong place. Each of those is avoidable.
Know this before you start
- The opt-in link only displays once the test's status is Published — not while it's in Draft or Pending publication.
- After you publish a test for the first time, the test link can take several hours to become available.
- Testers can't find a closed-test app by searching Google Play before it has an open or production release — you share the link with them.
- Testers can't leave public reviews on a test version, so you need to provide a feedback channel (an email address or URL).
On this page
Video: adding testers to your closed test
This short walkthrough covers the step people most often get wrong — adding a Google Group of testers to the closed testing track and copying the links testers use to join. The full written process, including what comes before and after, follows below.
What you need before you start
- An app created in Play Console under your personal developer account.
- A release-ready Android App Bundle (.aab) for the closed track.
- Any setup tasks Play Console flags on your app's Dashboard. Work through them first — outstanding required declarations can stop the release from going out.
- At least 12 testers with Google Accounts and Android devices — ideally a few more. Recruiting is its own job; see where to find testers.
- A feedback channel — an email address or URL. Google shows it to testers on the opt-in page.
Step-by-step: set up the closed test
- 1
Open the closed testing page
In Play Console, select your app and go to Test and release → Testing → Closed testing. Most apps already have a default closed track (often named Alpha). You can use it, or create a new track from the same page.
- 2
Open the track
Click Manage track on the track you'll use. Countries, testers and releases are all configured from here.
- 3
Choose countries / regions
Add every country your testers are in. If a tester's country isn't included for the track, they won't be able to get the app from it.
- 4
Add your testers
On the Testers tab, choose Email lists or Google Groups (compared below). For a list, enter the Google Account addresses your testers use on Google Play. For a group, enter its address in the format name@googlegroups.com — testers must join the group before they can opt in.
- 5
Add a feedback channel
Enter a feedback URL or email address. It appears on the opt-in page and is how testers reach you, since they can't leave public reviews on a test version.
- 6
Create and roll out a release
Create a new release on the track, upload your App Bundle, add release notes, then review and roll it out to the closed track.
- 7
Send the changes for review
Send the changes for review from Publishing overview. If Managed publishing is turned on, approved changes don't go live until you publish them yourself — easy to miss, and the track sits unpublished until you do.
- 8
Wait for Published, then copy the links
Once the track shows Published, scroll to How testers join your test on the Testers tab and copy the Join on Android and Join on web links. On a first publish, allow several hours before the link works.
- 9
Testers opt in and install
Each tester opens the link while signed in to the Google Account you added, accepts the invitation to become a tester, then installs the app from its Google Play page. Being on your list isn't the same as opting in — every tester has to do this step.
- 10
Track progress on the Dashboard
Your app's Dashboard is where you follow the closed-testing requirement and, once it's met, apply for production access. The 14 days are about testers being continuously opted in — not about when you created the track.
Email list or Google Group?
Both work for the requirement. The difference is who does the admin when testers change. A Google Group is what most testing services — including ours — ask you to add, because the tester roster can change without anyone editing your Play Console.
| Email list | Google Group | |
|---|---|---|
| How testers are added | You enter or upload each tester's Google Account email (CSV supported) | You add one group address; members of the group can opt in |
| Adding a tester later | Edit the list in Play Console | They join the group — no Play Console change needed |
| Extra step for testers | None beyond opting in | Must join the group before opting in |
| Limits | Up to 2,000 users per list, up to 50 lists per track | Membership is managed in Google Groups |
| Best for | A small, fixed group you already know | Rosters that may change, or a cohort shared via one address |
Setup mistakes that delay the 14 days
- Sharing the link before the track is Published. The opt-in link doesn't display in Draft or Pending publication, and a first publish can take several hours to become available.
- Managed publishing left on. Approved changes wait until you publish them manually.
- Testers on the wrong account. Access is tied to the exact Google Account on your list or in your group — not another account on the same phone.
- Testers also in your internal test. Google's docs say a user opted in to your internal test isn't eligible for your closed test until they opt out of the internal one. More in internal vs closed testing.
- Missing countries. Testers outside the track's countries/regions can't get the app.
- Group members who never joined. With a Google Group, testers must join the group first, then opt in.
- CSV upload rejected. Play Console doesn't accept CSV files saved as UTF-8 with BOM — re-save the file without BOM.
- Stopping at exactly 12. Testers who opt out before 14 days don't count, so one dropout puts you under the minimum. A few extra testers is cheap insurance.
After setup: make the 14 days count
Once 12 or more testers are opted in, the 14 days run. Use them: testers should be opening the app and sending feedback, because when you apply for production access Google reviews engagement and feedback — not just the headcount.
If Play Console shows fewer testers than you invited, start with why testers don't count. When the 14 days are up, our guide to production access questions covers the application itself.
Frequently asked questions
How long does it take to set up Google Play closed testing?
The Play Console steps take minutes once your app's setup tasks are done. The waiting is elsewhere: review of the release, and — after a first publish — up to several hours before the opt-in link becomes available. Plan for that, because testers can only start their 14 days once they can actually opt in.
Can testers find my app by searching Google Play?
No. Before your app has an open testing or production release, closed-test apps don't appear in Google Play search. Share the Join on Android or Join on web link with each tester directly.
Should I use an email list or a Google Group?
Either satisfies the requirement. Email lists suit a small, fixed group you already know. Google Groups suit rosters that may change during the test, since anyone who joins the group can opt in without you editing Play Console — testers just need to join the group before opting in.
Do testers need to install the app, or just opt in?
Google's published requirement counts testers who are opted in continuously for 14 days. But installing and actually using the app is what produces the engagement and feedback Google reviews when you apply for production access, so opting in alone is the weak version of a test.
Why doesn't my closed testing opt-in link work?
Usually the track isn't Published yet — the opt-in link only appears once the status is Published, not in Draft or Pending publication. After a first publish it can also take several hours to become available. If the track is live and a tester still can't join, check they're signed in with the account on your list.
Do testers have to pay for a paid app in a closed test?
Yes. According to Google, testers must purchase paid apps when taking part in open or closed tests. Only internal testers can install paid apps for free.
Official sources