Quick answer
In Play Console, open Testing, then Closed testing, and create or select a track. Under Testers, add an email list or a Google Group, save, and publish a release to the track. Then copy the opt-in link and send it to testers, who must accept it with the same Google account you added.
Before you start
- A Google Play developer account and an app created in Play Console.
- A signed app bundle that installs and opens reliably.
- Basic store listing details, content rating and app content forms completed as Play Console requires.
- The exact Google account email of every tester.
Menu names in Play Console change occasionally; the steps below describe the usual flow.
Step 1: Create the closed track
- Open your app in Play Console.
- Go to Test and release → Testing → Closed testing.
- Use the default closed track or create a new one, and give it a clear name such as "Launch test".
- Choose the countries where testers are located.
Step 2: Add your testers
You can add testers in two ways:
| Method | Good for | Watch out for |
|---|---|---|
| Email list | Small, fixed groups you manage directly | Typos in email addresses; testers using a different account |
| Google Group | Larger or changing groups; testers join the group themselves | Group settings must allow testers to join and view |
Add a feedback email or URL so testers know where to send feedback. Save your changes.
Step 3: Publish a release to the track
- Create a new release on the closed track and upload your app bundle.
- Add short release notes telling testers what to try.
- Review and roll out the release. Closed track releases go through Google's review before testers can install.
Step 4: Share the opt-in link
- Copy the opt-in link (web or Android) from the track's Testers section.
- Send it to testers with clear instructions: open the link while signed in to the exact Google account you gave, tap to become a tester, then install from Google Play.
- Ask each tester to confirm with a screenshot once they have joined and installed.
Need help writing those instructions? See how to write instructions testers can follow.
Step 5: Keep the test healthy
- Check your tester count daily, especially if you are working toward the 12-tester rule.
- Don't swap lists or groups mid-test — it can break your continuous count. See why the clock resets.
- Upload fixes to the same track as often as you need.
- Track your dates with our closed testing tracker.
Frequently asked questions
Why can't my tester see the app on Google Play?
Usually the tester is signed in with a different Google account from the one you added, hasn't accepted the opt-in link, or the release hasn't finished review yet.
Do testers need to be in my country?
Testers must be in countries you have made the track available in. Check your track's country settings.
Can testers use iPhones?
No. Google Play closed testing is for Android devices with Google Play.