Testers & opt-in

How to get 12 testers for Google Play: 5 ways

November 17, 2026 · 6 min read

A diverse group of young adults using smartphones in a casual indoor setting.
Photo by fauxels on Pexels

To get 12 testers for Google Play, recruit real people with Android phones from one or more of five sources: people you know, your existing users or community, tester-exchange groups, an open Google Group you promote yourself, or a managed testing service. Whichever you pick, each tester joins your closed track, opts in through your link and stays opted in for 14 continuous days. Most developers combine two sources and recruit a few extra people as a buffer.

The rule applies to personal developer accounts created after November 13, 2023: a closed test "with a minimum of 12 testers who have been opted in continuously for at least 14 days" (App testing requirements). Google's own advice on finding them is short: "Reach out to friends, family, colleagues, or classmates… Connect with communities where potential users exist… post about your app on social media." For what each route costs, see how much closed testing costs.

1. Friends, family and colleagues

How it works: you ask people you already know, collect their Google account emails and add them to an email list on your closed track.

Steps:

  1. Make a list of everyone you know who uses an Android phone. Aim for more than 12 names.
  2. Send a short personal message: what the app does, the 14-day commitment, and what you need (opt in, install, use it, report what breaks).
  3. Ask for the exact Google account they use on their phone, not a work address they never sign in with.
  4. Add the addresses to an email list in Play Console, then send each person the opt-in link once the track is live.

Effort: low to medium. Asking is quick; keeping busy people active for two weeks takes reminders.

Main risk: quiet dropouts and polite feedback. People who like you rarely say the app is confusing. Closed testing with friends and family covers this route in more depth.

2. Your existing users or community

How it works: if you have an audience (a newsletter, a Discord server, a social account, users of an earlier app), you invite them to try the new app early.

Steps:

  1. Write one clear post or email: what the app is, why you want testers, and the 14-day commitment.
  2. Add a simple sign-up step (a form or a reply) that collects the Google account email they use on Android.
  3. Add those addresses to your tester list, or ask them to join a Google Group you've attached to the track.
  4. Share the opt-in link in the same channel and pin it, so late joiners can find it.

Effort: medium. One announcement can bring in many people, but you still collect emails and follow up.

Main risk: not everyone has an audience yet. When you do, this is often the strongest source: Google recommends testers who "represent your app's intended future audience", and these people already care about what you're building.

3. Tester-exchange communities

How it works: developers in the same situation test each other's apps. In a developer forum, subreddit or chat group, people post their opt-in links; you test theirs, they test yours.

Steps:

  1. Read the group's rules first. Most expect you to test others before asking.
  2. Post your app with the opt-in link (or your Google Group address) and a one-line description.
  3. Opt in to other members' apps, install them and actually use them for the full period.
  4. Keep a simple sheet: who joined, on which date, with which account, and whose apps you owe a test.

Effort: high. You test other people's apps for two weeks too, and coordinate strangers.

Main risk: reciprocity fades. Someone who opts out on day 10 doesn't count, and some people opt in but never open the app. Never trade reviews or ratings in these groups. Google Play policy prohibits "fraudulent or incentivized reviews and ratings" (User Ratings, Reviews, and Installs), and testers can't leave public reviews on test versions anyway.

4. A Google Group you manage and promote

How it works: you create a Google Group, attach it to your closed track and let people join the group themselves instead of sending you emails. Google is clear that "Only members of the specified Google Groups can join your test" (Set up a test).

Steps:

  1. Create a group in Google Groups and set it so people can join without you adding them by hand.
  2. Add the group address ([email protected]) to your closed track's Testers tab, and send the change for review if it's waiting under Publishing overview.
  3. Share two links together wherever you post: the group's join page, then the opt-in link.
  4. Check group membership and opted-in numbers every few days.

Effort: low once set up. It pairs well with routes 2 and 3.

Main risk: setup mistakes. A tester who joined the group with one Google account but uses another on their phone will most likely be unable to get the app. Check the group's privacy settings too. Email list vs Google Group compares the two methods, and where to find the opt-in link explains what to share.

5. A managed testing service

How it works: you pay a company that supplies testers. Usually you add their Google Group or email list to your track and their country to the track's countries; they handle recruiting, reminders and replacing dropouts. GoPlayTester is one such service. Google's official documentation doesn't mention paid testing services, so read is paying for closed testers allowed first. No service can guarantee production access or shorten the 14 days; Google makes the final decision. Look for real people on real devices, and walk away from anyone offering reviews, installs or approval. Choosing a closed testing service has the full checklist.

The five ways side by side

Way Your effort Reliability Cost
Friends, family, colleagues Low to medium Medium: depends on reminders Free
Your users or community Medium High if you have an audience Free
Tester-exchange communities High Low to medium: dropouts are common Free
Google Group you promote Low once set up Depends on who joins Free
Managed testing service Low Depends on the provider Paid

For prices and what you'd be paying for, see the cost article.

How many testers to recruit

Google's number is 12, and it's measured when you apply: at least 12 testers must be opted in at that moment, each continuously for the preceding 14 days. Anyone who opts out early stops counting, and opting back in restarts their 14 days.

So recruiting exactly 12 is risky. Our advice, not a Google rule: aim for a few more, so one lost phone doesn't push you below the minimum. Once testing starts, keeping the app installed and using it regularly is strongly advised, because Google lists "insufficient tester engagement" as a reason to require more testing. Keeping testers engaged for 14 days has practical ideas.

Checks before day 1

Most lost days happen before anyone opts in. Check:

  • The closed release is published. "The opt-in link displays only when an app status is 'Published'", and after the first publish the link "can take several hours to become available."
  • Countries include your testers. Testers in a country you haven't selected for the track will most likely be unable to get the test.
  • Every tester has the right account. "Users need a Google Account or a Google Workspace account to join a test," and they should use the same account you added to the list or group.
  • Your instructions are ready. One message with the opt-in link, the install step and the 14-day commitment. Google also suggests a messaging group for testers.
  • You track joins. Note each tester's join date so you know when their 14 days started.

Key takeaways

  • Five sources work: people you know, your audience, exchange groups, a self-promoted Google Group, or a paid service.
  • Recruit a buffer above 12, check the track is live first, and keep testers active for 14 continuous days.

If you'd rather hand recruiting off, the order page shows how our service works, and the setup guide walks through the Play Console side either way.

All articles