Where to find 12 testers: free and paid options
In short: the first place Google suggests is your own network: friends, family, colleagues and classmates. Next come the communities where your target users are, and social media. If that isn't enough, there are paid testing providers; Google itself mentions this option in the application form. Whichever route you take, 12 people need to stay opted in for 14 days in a row.
12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.
See packsWhat does Google suggest?
“The most common way to recruit testers is to use personal and professional networks. Reach out to friends, family, colleagues, or classmates to ask them to test your app.”
Play Console Help, testing requirements page
Google's other suggestions: connect with communities where potential users are (Google's example: for a fitness app, local clubs and online groups), and post on social media and invite followers to sign up for testing. And on who to look for: “Recruit testers who represent your app's intended future audience.” According to Google, the closer your testers match your target audience, the more useful their feedback.
Free options
- Your own network. You get real use and real feedback. Each person needs an Android phone and a Google Account, and must not leave the test for 14 days.
- Your target audience's communities. Clubs, associations, online groups. You reach people who would actually use the app.
- Social media. Invite your followers to the test and share the opt-in link.
- Test exchange communities. There are also groups where developers test each other's apps; Google's pages don't mention them. Watch out: “Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement.” Since you can't know who will leave and when, start with more than 12 people.
Whichever route you take, Google's advice is the same: “Inform your testers that they need to remain opted in to your closed test continuously for at least 14 days.” Give them clear instructions and set up a feedback channel; the application form asks about both.
Paid options
In the first question of the application form, Google itself mentions paid testing providers. The text in Play Console's English interface:
“How did you recruit users for your closed test? For example, did you ask friends and family, or use a paid testing provider?”
Play Console, production access application form, part 1 (seen in our own app in November 2026)
Google's help pages say nothing else about paid testing services. TesterPass offers this service too; weigh us against the questions below as well.
Questions to ask
- Who are the testers, and how does the test run? The service should explain this openly.
- Can you follow every day? How many people are opted in, and who opened the app on which day. You should be able to compare this with the opted-in count Play Console shows.
- Does it ask for your Play Console password or account access? Adding testers doesn't need it: you enter the group address or list in your own Play Console, and testers opt in themselves through the opt-in link.
- Does it promise approval? Google decides on production access and may ask for more testing. A promise that guarantees approval claims to know Google's decision in advance.
- What does it base the form answers on? On your test's record, or the same ready-made sentences for everyone? The form answers are submitted in your name; don't write about engagement or feedback that didn't happen in your test.
- When do the testers leave? 12 people must still be opted in when you apply; find out in advance which day they leave.
- What does the refund promise cover? What happens if 12 people don't complete the 14 days should be in writing.
Google's relevant policy
Google Play's “User Ratings, Reviews, and Installs” policy: “We prohibit any manipulation of ratings, reviews, or install counts. This includes incentivizing feedback, using forced pop-ups, or paying for fake reviews.” The same page's “Key Considerations” section adds: “Don't use automated services to inflate installs or ratings.” Don't ask testers for store ratings or reviews.
Feedback in a closed test doesn't count toward your store rating: “Feedback from your test users won't affect your app's public rating.”
Sources
- App testing requirements for new personal developer accounts
- Set up an open, closed, or internal test
- User Ratings, Reviews, and Installs
Play Console Help and policy pages. The form question is quoted word for word from our own app's application window in Play Console's English interface (November 2026). The “Questions to ask” list is our suggestion, not Google's.
12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.
See packs