How to get 12 testers for Google Play closed testing
Google requires 12 testers opted in for 14 consecutive days before production access. Here are the four ways to find them, and the trade-offs of each.
What Google actually requires
If your personal developer account was created after 13 November 2023, you must run a closed test with at least 12 testers opted in for 14 consecutive days before you can apply for production access. Organisation accounts are exempt. Every new app clears the requirement separately - passing once does not carry over.
The word doing the work in that sentence is opted in. Adding twelve email addresses to a tester list does nothing on its own. Each of those people has to open your opt-in link and accept. Google counts acceptances, not invitations, and this is where the majority of self-organised tests quietly fall short.
Option one: people you already know
Free, and the obvious first move. It also has the worst completion rate of anything on this list. Twelve friends with Android phones is a tall order in markets where iOS dominates, and the ones who do accept tend to open the app once out of politeness and never again.
Google's reviewers look at engagement across the window, not just the opt-in count on day one. A test where all activity happens in the first 48 hours reads as a box-ticking exercise, because that is what it is.
Option two: developer communities
Reddit threads, Discord servers and Telegram groups run informal tester swaps: you test mine, I test yours. It costs nothing but your own time, and reciprocity is the whole mechanism - you are committing to fourteen days of testing someone else's app for every person who tests yours.
Quality varies. Swap partners drop out mid-window without warning, and you have no recourse when they do. Budget for attrition by recruiting well above twelve.
Option three: freelance marketplaces
Gig marketplaces will sell you testers cheaply. The risk is what you are actually buying: bulk-created Google accounts, emulator farms, and device fingerprints that repeat across hundreds of unrelated apps.
Google detects this reliably, and the consequence is not a failed test - it is enforcement against your developer account. Ask any seller how their testers are sourced, and treat a vague answer as an answer.
Option four: a dedicated testing service
A service exists to make the 14-day window a scheduling problem rather than a social one. The things worth checking before you pay anyone: are the testers real people on their own devices, is activity paced across the full window, and what happens if Google still says no.
Whatever you choose, recruit above the minimum. Twelve exactly means one dropout puts you under the line on day thirteen with no time to recover.