Field log · Play Console
Where to actually find 12 testers for closed testing
The rule is one sentence: 12 testers, opted in, for 14 days. Satisfying it is a different thing entirely, because the hard part isn't the number — it's finding twelve real people who will opt in properly and not vanish. Here's where I looked, what actually worked, and what wasted my time.
If you made a personal Google Play developer account recently, you can't reach production until you've run a closed test with at least 12 testers who stay opted in for 14 continuous days. I've written separately about the mechanics and the trap that resets the clock — this post is about the part everyone actually gets stuck on: who are these twelve people?
First, the definition that makes recruiting harder than it sounds: a tester only counts once they open your opt-in link, accept, and install under the same Google account they accepted with. "I'll test it for you" from a friend who never installs counts as zero. So you're not looking for twelve yeses — you're looking for twelve completed opt-ins. Recruit accordingly.
Recruit more than twelve — a lot more
The single most useful thing I did was stop treating twelve as the target. Between people who say yes and never finish, people on iPhones who can't help, and people who install once and drift, the completion rate on invites is low. Aim for fifteen to twenty committed opt-ins so that normal drop-off doesn't drag you back under the line and reset your streak. Padding the roster is cheaper than restarting the clock.
Where the testers actually came from
People you already know
The least glamorous source is the most reliable: friends, family, coworkers, anyone with an Android phone who'll follow two links. They won't give you great feedback, but for clearing the requirement they're solid because they'll actually complete the opt-in when you walk them through it. The catch is you need enough Android users in your circle — if most of your people are on iPhones, this dries up fast and you move to the next options.
Tester-exchange communities
There are communities built specifically around this rule, where developers test each other's apps to clear the same requirement. Reddit has active threads for it, and there are dedicated groups and Discord/Telegram servers where you swap installs — you test twelve of theirs, they test yours. It's the fastest way to hit the number if your personal network is thin. Two cautions: read each community's rules before posting, and understand these testers are clearing a requirement, not evaluating your app — so treat their "activity" as box-checking, not real feedback.
Your own audience, if you have one
If you have any following — a small YouTube channel, a dev-community presence, users of your other apps — a direct call for testers works and brings people who might actually care about the app. For a first-time developer this is usually the smallest source, but it produces the best testers, because they opted in out of interest rather than reciprocity.
The mistakes that cost me testers
- Wrong target countries. If your closed-testing track's country list doesn't include where your testers live, they open the link and see "app not available." Set the countries to cover your actual testers before you send a single invite — this one silently wastes people.
- No walkthrough. The opt-in flow (open web link → accept → install from the Store under that account) is not obvious to non-developers. Send a two-line instruction with the exact steps, or half your recruits stall at the install step and never count.
- Assuming an install is permanent. Uninstalling doesn't remove someone's opt-in, so your raw count can look fine while your testers have all quietly left. That reads as "no real testing" at review time. Nudge them to actually open the app once or twice during the window.
- Recruiting exactly twelve. One opt-out drops you to eleven and puts the streak at risk. The buffer isn't optional; it's insurance.
Keeping them for the full 14 days
Getting to twelve is day one; staying at twelve for fourteen continuous days is the actual task. A few things that helped: push at least one small update during the window so the test looks alive rather than frozen; send a single friendly reminder partway through so install-once-and-vanish testers reopen the app; and keep a couple of spare recruits warm in case someone opts out. And the discipline from the mechanics post applies here too — once the clock is running, don't re-apply early, or you can reset the very window your testers are helping you complete.
None of this is about the quality of your app. It's a logistics problem: find more than twelve Android users, make opting in idiot-proof, cover the right countries, and protect the count for two weeks. Do that and the gate opens on schedule. Treat it as recruiting rather than engineering and it stops feeling unfair — it's just a checklist with people in it.
Google's testing requirements and numbers have changed before and can change again; confirm the current rule on the Play Console Help pages before planning around specific figures.