How to find 12 testers for your Google Play closed test

What Google actually expects from your 12 testers

If your personal developer account was created after November 13, 2023, Google requires at least 12 testers opted in to your closed test continuously for the 14 days before you apply for production access. The threshold used to be 20 testers until it was lowered to 12 in late 2024.

For Google, a tester is a Google account that joined your test through the opt-in link. Adding an address to the list isn't enough: the person has to open the link with that account and accept. So you're looking for people with an Android device, a Google account, and enough motivation to stick around for two weeks.

• An Android device with the Play Store, to install the app from Google Play.
• A Google (or Google Workspace) account on your tester list or in your Google Group.
• Opting in through the "Join on the web" link, then not opting out for 14 days.
• Real usage: Google can deny production access if tester engagement looks insufficient.

The rule and the setup are covered in our 12 testers rule guide. This page answers one question only: where to find those 12 people.

5 ways to find testers

1. People you know: family, friends, coworkers

It's free and the most reliable over two weeks, because people you know will answer when you nudge them. The catch: many of them don't use Android (an iPhone doesn't count), and few will really use an app that isn't meant for them. Pick people close to your app's audience and tell them up front that they need to stay opted in for two weeks.

2. Your future users: waitlist, social accounts, app community

If your app already has an audience (newsletter, social account, Discord server, customers of an existing service), that's your best source: Google itself recommends recruiting testers who represent your intended audience. Their feedback will also be the most useful for your updates, and for the production access questions.

3. Developer communities

Android developer forums and groups are full of "I'll test yours if you test mine" posts. It works, but engagement varies: many people opt in, open the app once, then opt out to make room for other tests. Plan for extra testers and keep a close eye on your count.

4. Test exchange apps

Some apps run the exchange for you: you earn credits by testing other developers' apps and spend them to get testers. It costs no money but plenty of time, since you need to open several apps every day for two weeks. And your testers won't necessarily look like your audience.

5. A managed testers service

You pay a flat fee, get a group of testers to add in Play Console, and the provider keeps them opted in. It's the fastest route when your own circle isn't enough. Services differ a lot, though: real devices or not, how long they actually cover, whether they replace testers who drop out, and what reporting you get.

To compare prices and what they include, see how much a Google Play testers service costs.

Which option fits your situation

• You already have users: recruit them first, it's the closest thing to real-world usage.
• You have 12 motivated Android users around you: that's enough, as long as you follow up for 14 days.
• You have time but no budget: communities and test exchanges, with at least 15 to 20 opt-ins to absorb dropouts.
• You want to start fast and skip the follow-up: a managed service, after checking what it really guarantees.
• Often a mix works best: a few real users for feedback, topped up to reach the threshold.

Inviting testers without losing them

1. 1

   Pick an email list or a Google Group

   An email list is managed in the closed test's Testers tab (up to 2,000 addresses per list). A Google Group is more flexible: anyone can be added without touching Play Console, and the group has no size limit. Members must join the group before they opt in to the test.

2. 2

   Publish the release before sharing the link

   The opt-in link only works once the test release is published. Sending it too early shows an error page and loses testers on day one.

3. 3

   Get everyone opted in on the same day

   The 14-day window depends on testers being opted in continuously: if tester number 12 joins on day 5, your countdown starts on day 5. Set a launch date and chase latecomers.

4. 4

   Check which account they use

   Many testers have several Google accounts on their phone. The link must be opened with the account you added, and the app installed from the Play Store with that same account.

Pitfalls to avoid

• Aiming for exactly 12: a single opt-out restarts your 14-day window. Recruit 14 or 15 if you manage testers yourself.
• Recruiting people without an Android device, or who never use it.
• Asking for Google Play ratings or reviews in exchange for anything: Google's policy bans rewards for reviews and any manipulation of ratings and installs.
• Forgetting to target your testers' country under "Countries/regions" for the closed track: they won't be able to install the app.
• Requiring a login without giving testers demo credentials: they can't test anything.
• Publishing nothing for 14 days: without updates, it's hard to show Google you acted on feedback.

The mistakes that lead to a production access refusal are covered in our article on the 14-day closed test.

Finding your 12 testers with PlayTesterHub

If your own circle isn't enough, PlayTesterHub runs your closed test on 12 physical Android devices managed in-house by our team in France: no bots, no emulators. You add the email group we give you in Play Console, testing starts within 8 hours of your confirmation, and if a tester drops out, we replace them. You can also combine your own testers with ours.

Flat price shown before payment, no subscription. PlayTesterHub does not guarantee Google Play approval: Google alone decides.