How Do I Invite Testers to a Closed Test on Google Play?

Three steps: create an email list under Testing then Closed testing, publish the release, and share the opt-in link with your testers.

The part that catches almost everyone: adding someone’s email address does not invite them to anything. Google sends no notification. Until that person opens your opt-in link and clicks Become a tester, they are not opted in and they do not count toward your 12.

Half the work is yours and half is theirs. Most failed tests stall on the right-hand column.

How do I add testers with an email list?

This is the simplest method and the one we recommend.

In Play Console, open your app and go to Testing > Closed testing, then select Manage track.
Open the Testers tab and select Create email list.
Name the list. Lists are reusable across your apps, so name it something you will recognise later.
Add the addresses, either separated by commas or uploaded as a CSV with one email per line.
Select the list in the Testers section, add a feedback contact email or URL, and save.
Copy the shareable opt-in link.

Google’s limits are generous: up to 200 email lists in total, a maximum of 50 lists per track, and up to 2,000 users per list [1]. For a 12 tester requirement you will never come close.

Because lists are reusable, building one good list of 14 to 16 people means you can paste it into every future app. More on that in our guide to whether you need new testers for every app.

How do I use a Google Group instead?

Use a group if you want people to be able to join and leave without you editing a list each time.

Follow the first three steps above.
In the Testers section, choose Google Groups.
Enter the group address in the form yourgroupname@googlegroups.com.
Add your feedback contact details and save, then copy the opt-in link.

One rule to know: only members of that group can join the test, and they must join the group before opting in [1]. If a tester opens your link before their group membership is approved, they will be told the app is not available.

This is the most common cause of Google Group tests appearing broken. It is almost never the link. It is membership order.

Where is my opt-in link?

If you cannot find the link, this is almost certainly why: the opt-in link only appears once your app is published. While the release sits in Draft or Pending publication, there is no link to copy [1].

Two related delays are worth planning around, both stated in Google’s documentation:

After you first publish, it can take a few hours for the test link to become available.
After you change your tester list, changes can take several hours to reach testers [1].

So a tester who says the link does not work twenty minutes after you added them is probably not doing anything wrong. Wait a few hours before troubleshooting anything else.

What does the tester actually have to do?

Send them these three steps, because assuming they know is how tests stall:

Open the opt-in link while signed into the exact Google account you added. Not their work account, not a second account on the same phone.
Click Become a tester. This is the actual opt-in. Nothing before this counts.
Install the app from the Play Store page the link leads to.

Only after step three does that person contribute to your test.

Why can my testers not see the app?

Nearly every case is one of these:

Signed into a different Google account than the one on your list. Ask them to check which account the Play Store is using.
They have not clicked Become a tester yet. Opening the link is not the same as opting in.
Not yet a member of the Google Group, if you used the group method.
Changes have not propagated. Give it several hours.
The release is not actually live on the closed track, or the country they are in is not included in the track’s countries.

How do I check who has actually opted in?

Play Console shows an opted-in tester count on the closed testing track. That number is the only one that matters, and it moves only when someone completes the opt-in.

Confirm the count reaches 12 or more before you start counting your 14 days. A test where you assumed everyone joined on day one, and they actually joined on day four, finishes four days later than you planned.

A short checklist before you send the invite

Release is published on the closed testing track, not sitting in Draft
Email list saved with 14 to 16 addresses, not exactly 12
Feedback contact email or URL filled in
Opt-in link copied and tested by you first
Message to testers includes the link, the account rule, and the Become a tester step
Play Console tester count checked a few hours later, before day one

Frequently asked questions

Does Google email my testers automatically?

No. Google sends nothing. Adding an address to a list only makes that person eligible. You have to send the opt-in link yourself.

How many testers can I add?

Up to 2,000 per email list, with up to 50 lists per track and 200 lists in total [1]. The requirement is a minimum of 12, not a maximum.

Can I reuse an email list for another app?

Yes. Email lists are reusable across your apps. Your testers will still need to opt in separately for each app.

Can testers use any email address?

It has to be a Google account, because opting in and installing both happen through the Play Store.

How long after adding a tester can they install?

Allow several hours. Google states that changes to your tester list can take several hours to take effect [1].

Do testers need the link every time I release an update?

No. Once someone has opted in, updates reach them automatically like any other app update.

What if a tester cannot find Become a tester on the page?

They are usually signed into a different Google account, or the app is not published yet. Check both before anything else.

What if I do not have 12 people to invite?

Inviting testers is the quick part. Finding 12 people who will open a link, opt in on the correct account, and then keep using your app for 14 days is what turns a two week test into a two month one. There are two ways around it.

Option 1: have the testers assigned to you

Opt for one of our plans and the whole right-hand column of that diagram stops being your problem.

Starter, ₹999 gives you 15 verified Android testers for the full 14 days.
Pro, ₹1,699 gives you 25 testers, plus a detailed ASO report and priority support.

Testers assigned within 6 hours, already opted in on the right accounts, so your day one is actually day one.
They stay active across the full period rather than installing once and disappearing.
Anyone who goes inactive is replaced, so a dropout never quietly costs you days.
A feedback report at the end, plus pre-filled answers for the 10 production access questions.
100% production access or your money back.

More than 10,000 apps have reached production this way. Submit your app to start.

Option 2: join a free Pack of 16

If you have more time than budget, the Testers Community app is free and runs on mutual testing. You join a Pack of 16 developers who test each other’s apps for 16 days, opening every app daily and leaving real feedback. Everyone in the pack needs production access for their own app, so the incentive lasts the full run, and members who stop testing are replaced. The cost is your time: you are testing fifteen other apps while yours is being tested.

Either way, read the full closed testing requirements before you start your 14 days.