Getting 12 people to opt in is the easy part. Getting 12 people who stay opted in for 14 days — and actually use your app — is where most closed tests struggle. Here's where developers find testers, what each source is good for, and how to keep the testers you recruit.
What Google asks of your testers
- At least 12 testers, opted in continuously for at least the 14 days before you apply for production access.
- Google suggests recruiting through your personal and professional networks, and recruiting a diverse group of testers.
- Give testers clear instructions and a clear feedback channel, such as email, a website, or a messaging forum.
On this page
What makes a good tester
- Has an Android device and a Google Account — and will opt in with the account you added.
- Will stay opted in for the full period, not just the first day.
- Will actually open and use the app, because Google reviews engagement and feedback when you apply.
- Is a real person on a real device. Bots, scripted accounts and emulators put your account at risk — see whether hiring testers is against policy.
6 places to find testers
| Source | Good for | Watch out for |
|---|---|---|
| Friends and family | Fast, free and trustworthy | Not everyone uses Android; engagement often fades after the first few days |
| Coworkers and professional network | Google's own suggestion; often more considered feedback | Busy people forget — plan to send reminders |
| Your users, waitlist or followers | Testers who genuinely care about the app | Only works if you already have an audience |
| Communities about your app's topic | Testers who resemble your real users | Read each community's self-promotion rules first |
| Developer tester-exchange groups | Free — you test their apps, they test yours | Testers often opt in once and drift away; you owe testing in return |
| Managed testing services | No recruiting or chasing; testers for the full period | Costs money; check testers are real people on real devices |
Friends, family and coworkers
This is where Google suggests starting, and it's the most trustworthy pool you have. The catch is numbers and stamina: few people have a dozen Android-using friends willing to open a test app for two weeks. Ask early, ask more than 12, and give them a two-line brief — opt in, install, use it a few times, tell you what's broken.
Your own audience
A newsletter, waitlist, social following, or users of an earlier app are the best source there is: people who chose to care about what you're building. Their feedback is also the closest preview of what real users will say after launch — useful material for the feedback questions in the production access form.
Communities around your app's topic
Communities built around your app's subject — not just developer forums — get you testers who look like your eventual users, which also helps with the diverse group Google recommends. Read each community's rules before posting; many restrict self-promotion, and a post that reads like an ad tends to get removed.
Tester-exchange groups
Developer communities on Reddit, Discord and Telegram run reciprocal "test mine, I'll test yours" exchanges. They're free, and they can work. They're also where developers most often report the problems that sink closed tests: testers who opt in once, never open the app, and leave before day 14. If you use them, recruit well above 12 and keep an eye on your count.
Managed testing services
A managed service recruits, enrolls and coordinates testers for you. Using one isn't against Google Play policy in itself — what matters is that the testing is genuine. When comparing services, ask three things: are the testers real people on physical devices, do they use the app across the full 14 days, and will you get feedback you can use in your production access answers?
If that's the route you want, our closed testing service enrolls real Android testers above the 12 minimum and delivers a written QA report — there's a worked example in our Sea Guardian case study.
How to keep testers for the full 14 days
- Recruit a buffer above 12 — dropouts are normal.
- Send one clear message: which account to use, the opt-in link, and what you'd like them to try. Google recommends giving testers clear instructions.
- Give them one feedback channel — an email address, form or group chat — and set it as the feedback URL in Play Console.
- Check in a few times during the 14 days with something specific to try, like a new feature or a bug you've fixed.
- Ask them not to opt out until you've applied — testers who opt out before 14 days don't count.
- Thank them, and tell them when the app launches.
Frequently asked questions
How many testers should I recruit for Google Play closed testing?
Google's minimum is 12, continuously opted in for 14 days. Because a tester who opts out early stops counting, recruit a buffer above that — a few extra people is much cheaper than restarting the clock.
Can I use tester-exchange groups on Reddit or Discord?
Yes — nothing in Google's requirement prohibits it, and the testers are real people. The risk is reliability: reciprocal testers often opt in and drift away. Recruit extra, monitor your count, and make sure testers genuinely use the app.
Is it against Google Play policy to pay for testers?
How you recruit isn't what Google evaluates — whether the testing is genuine is. Real people on real devices using the app is fine; bots, emulators and fake engagement are not. Our policy guide covers where the line actually is.
Do my testers need to be in my country?
No, but each tester's country needs to be included in your closed track's countries/regions, or they won't be able to get the app from that track.
Do testers have to give feedback?
Google's published requirement is about how long testers are opted in, but Google recommends giving testers a clear feedback channel, and the production access application asks about your closed test. Real tester feedback is what lets you answer those questions specifically and honestly.
Can my testers use emulators?
Avoid it. The test should reflect genuine use on real devices; emulators and scripted accounts look like non-genuine activity and put your developer account at risk.
Official sources