A tester joins your closed test in three moves: they open your opt-in link while signed in with the Google account you added, they accept the invitation on the page that explains tester responsibilities, and then they install the app from Google Play. Only after accepting are they opted in. Knowing exactly what they see makes it much easier to help when someone gets stuck.
This article is from the tester's side. For your side of the setup, see how to create a closed testing track.
What has to be true before a tester can join
Three things need to be in place on your end, or the tester hits an error no matter what they do:
- The tester's Google account is on your list. Either their email is on an email list attached to the track, or they're a member of the Google Group you added. "Users need a Google Account or a Google Workspace account to join a test" (Set up a test).
- The track is published. The opt-in link only shows in Play Console when the app status is "Published", not Draft or Pending. That means you've sent the changes for review and Google has approved them. If you haven't pressed send, here's what's going on.
- The tester's country is included. If their country isn't selected for the closed track, they likely can't get the app.
Also note: after you publish a test for the first time, the link "can take several hours to become available to testers." An error in the first few hours isn't necessarily a mistake.
The tester's steps
Step 1: Sign in with the invited account
Before opening the link, the tester should check which Google account is active in their browser and in the Play Store app on their phone. Many people have two or three Google accounts. They must use the Google account you added to the list. If they open the link with a different account, it most likely won't recognize them as an invited tester.
Step 2: Open the opt-in link
You share one link with everyone. Play Console offers a link that opens on the web and one meant for Android devices; both lead to the same invitation. The tester can open it on their phone or on a computer.
Step 3: Accept the invitation
Google's help page describes it this way: "After clicking the opt-in link, testers receive an explanation of tester responsibilities and a link to opt in. Each tester needs to opt in using the link." The tester reads the page and taps the button to become a tester. The page then confirms they've joined.
This acceptance is the moment that matters for the requirement. Being on your email list or in your Google Group isn't enough by itself; each tester has to opt in.
Step 4: Install the app from Google Play
After opting in, the page offers a link to download the app on Google Play. The tester installs it like any other app, on an Android device signed in with the same account. The Play Store listing may show that they're a tester for this app.
If your app is paid, note that closed testers "must purchase paid apps"; only internal testers install them for free.
Step 5: Use the app and send feedback
Testers can send private feedback to you through Google Play. That feedback "won't affect your app's public rating," and testers can't leave public reviews on test versions. You'll find it in Play Console under Monitor and improve > Ratings and reviews > Testing feedback.
Step 6: Stay opted in
For the 12-tester, 14-day requirement, testers need to stay opted in continuously for 14 days. Someone who opts out early doesn't count. Keeping the app installed and using it regularly is strongly advised, because Google can ask for more testing if tester engagement is too low (App testing requirements).
A message you can send your testers
Something short works best:
Thanks for testing! 1) Make sure your phone's Play Store uses the Google account I added. 2) Open this link and tap the button to become a tester. 3) Install the app from the Google Play link on that page. 4) Please keep it installed and open it now and then for the next 14 days. Send feedback any time.
When a tester says "it doesn't work"
Ask these questions in order:
- Which Google account are you signed in with? Compare it with the address on your list.
- What exactly does the page say? An error that the app isn't available usually points to the track not being published yet, a missing country, or the wrong account.
- Did you tap the opt-in button? Some testers read the page and stop there, so they never actually opt in.
- Is your country on the track? Check the Countries/regions tab.
Key takeaways
- Testers must be on your list, use that same Google account, and accept the invitation.
- The link only works after the track is published, and the first publish can take hours to propagate.
- Opting in is what counts; installing and using the app is strongly advised.
- Feedback is private and never affects your public rating.
GoPlayTester testers already know this flow and opt in with the accounts in our Google Group, so you don't have to coach 12 people through it. Follow our setup guide or order here.
