How testers join a Google Play closed test

To join a closed test, a tester needs four things: a Google account the developer allowed in, the opt-in link, the same account signed in to the Play Store on an Android phone, and the patience to stay opted in for 14 days. Most failures come from mixing up accounts or opening the link too early.

This page is written for testers, and for developers who need to explain the process to them.

Before you start: one Google account

Google says users need a Google Account or a Google Workspace account to join a test (Play Console Help).

Pick one account and use it for every step below. If your phone has several Google accounts, note which one the Play Store uses. That's the account that has to be a tester.

Step 1: Get access from the developer

The developer controls who can join. There are two common ways.

Google Group. The developer adds a group to the closed track. You join the group with your Google account, usually at groups.google.com. Google is explicit: "For closed tests using a Google Group, users must join the group before opting into your test" (Play Console Help). If the group asks the owner to approve new members, wait until you're approved.

Email list. The developer types your exact Gmail address into a tester list. Nothing to do on your side, but the address must match the account on your phone.

Step 2: Open the opt-in link

A closed test opt-in link looks like this (Play Console Help):

https://play.google.com/apps/testing/com.example.app

The last part is the app's package name. Open it in a browser where you're signed in with the same Google account.

The page explains what being a tester means and shows a button to opt in. Each tester has to opt in personally through this link (Play Console Help). Being in the group or on the list is not enough.

Two timing rules from Google:

• The link only exists once the app's status is "Published". Draft or pending apps don't have one.
• After the developer publishes the test for the first time, the link can take several hours to work.

If you tried during that window, try again later before assuming something is broken.

Step 3: Install the app from Google Play

After opting in, install the app from Google Play on your Android phone. The opt-in page links to the app's Play Store page.

Don't search for the app by name. Google says testers "cannot find your app by searching Google Play" during internal or closed testing (Play Console Help). Use the link.

If the Play Store shows an error instead of an install button, check:

• Account. In the Play Store, tap your profile picture and make sure the tester account is active.
• Group. Your membership may still be pending.
• Internal test. If you previously joined this app's internal test, you're not eligible for the closed test until you leave the internal one (Play Console Help).
• Country and device. The app may not be available in your country, or your device may not meet its requirements.

Error-specific guides: Item not found and App not available.

Step 4: Stay opted in for 14 days

This is the part that matters for the developer. Google requires at least 12 testers "who have been opted in continuously for at least 14 days" (Play Console Help).

Google also says: "If a tester opts out and opts back in later, the 14 days must be consecutive to count." So leaving on day 10 and rejoining on day 11 sends your personal count back to zero.

While you're in:

• Keep the app. Updates arrive automatically. Google says the app updates to the test version within a few minutes of installation.
• Use it. The developer will have to describe in Google's form whether testers used the features, so real usage helps them.
• Send feedback through the channel the developer gives you (email, form, chat), or privately through Google Play.

To send private feedback in the Play Store: profile icon, Manage apps & devices, Beta, open the app, then Write feedback under "Private feedback to developer". Only the developer sees it (Google Play Help). Google says feedback from test users won't affect the app's public "rating" (Play Console Help).

Leaving a test

When the developer says you're done, you can leave: profile icon, Manage apps & devices, Beta, open the app, then Leave under "You're a beta tester" (Google Play Help). To go back to the public version later, uninstall the test version and install it again from the public listing.

Google warns that you may lose progress or settings when you leave and uninstall a beta app.

For developers: what to send your testers

Most failed opt-ins come from unclear instructions. Send each tester one message with:

1. The Google Group link (if you use one) and a line saying "join with the same Google account your phone uses".
2. The opt-in link, copied from Play Console: Test and release > Testing > Closed testing > Manage track > Testers tab.
3. The time commitment: stay opted in 14 days in a row, don't leave and rejoin. Google recommends telling testers this directly (Play Console Help).
4. What to test: two or three concrete tasks, not "try my app".
5. Where to send feedback: one channel. Google also lets you show a feedback URL or email on the opt-in page.

A short template:

Thanks for testing! 1) Join this group with the Google account on your phone: [group link]. 2) Open this link and opt in: [opt-in link]. 3) Install from the Play Store page it shows. Please stay in for 14 days without leaving. Each day, try: [task]. Send bugs to [channel].

Then track who actually opted in. A tester who joined the group but never opened the opt-in link doesn't count.

For the bigger picture, see the Google Play closed testing guide and how the 14 days are counted.