How to set up a Google Play closed test, step by step (2026)
By Sabahattin Sudan, founder of SwapTesters · Updated October 14, 2026 · 4 min read
Before you can count to 12 testers and 14 days, the closed test has to work: testers must be able to find the invitation, opt in and install. This guide walks through the setup in Play Console and the small mistakes that leave testers staring at a “not available” page.
Step 1: Open the closed testing track
- In Play Console, select your app and go to Test and release › Testing › Closed testing.
- Click Manage track on the existing closed track (you can also click Create track to add another one, but one is enough for the 12-tester requirement).
Step 2: Choose countries
Make sure every country your testers are in is selected. If a tester's country isn't available, they won't be able to install the app even after opting in. Google notes that additional closed tracks don't support their own country targeting, so set countries on the main closed track.
Step 3: Add your testers
You have two options. You can use either, or both.
| Option | How it works | Best for |
|---|---|---|
| Email list | Click Create email list, give it a name and add addresses separated by commas, or upload a CSV | A small, fixed group you know by email |
| Google Group | Create a group at groups.google.com and enter its address (name@googlegroups.com) | Changing groups — people join the group themselves, you don't edit the list |
- Uploading a CSV replaces the addresses already in that list — it doesn't add to them.
- With a Google Group, testers must join the group first, then opt in to the test.
- Limits are generous: up to 2,000 users per email list and up to 50 lists per track.
Step 4: Add a feedback channel
Enter a feedback email address or URL (a Google Form works well). It appears on the page testers see when they opt in. You'll need this feedback later: the production access application asks what feedback you received and how you collected it.
Step 5: Create and roll out a release
Create a release on the closed track, upload your .aab, add release notes and roll it out. The opt-in link only appears once the test is published, and Google says it can take several hours after the first publish before the link works for testers. Don't send invitations until it does.
Step 6: Share the opt-in link
- Copy the opt-in link from the Testers tab of the closed track.
- Send it to your testers. Each one opens it, reads what testers are expected to do and taps to become a tester.
- They then install the app from Google Play. After that, updates to the test version arrive automatically, usually within minutes.
Remember: for the production requirement, Google counts testers who opted in, and each one needs 14 days in a row. Track the date each person joined.
Why testers can't join — and how to fix it
| What the tester sees | Likely cause | Fix |
|---|---|---|
| “App not available” / no install button | Signed in to Google Play with a different account than the one you invited | Ask them to switch account in the Play Store, or add their Play account address |
| The link doesn't open anything | The release isn't published yet or is only a few hours old | Wait until the track is published and try again later |
| “Not available in your country” | Their country isn't selected | Add the country to the closed track |
| Can't opt in with a Google Group | They haven't joined the group | Send the group link first, then the opt-in link |
Good to know
- Testers can't leave public reviews for test versions, and their feedback doesn't affect your public rating. Feedback reaches you privately.
- If your app is paid, testers in a closed test have to buy it.
- To stop a test, use Pause track — but don't pause during your 14 days.
Setup done? Next, read how Google counts your testers in the 12 testers, 14 days guide.
Source: Play Console Help — Set up an open, closed or internal test. Checked on 14 October 2026; Play Console menu names change from time to time.