Find 12 Testers for Your Google Play Closed Test
New personal Play Console accounts cannot publish until 12 testers have been opted in to a closed test for 14 continuous days. Most solo developers do not know 12 people with an Android phone who will keep an unfinished app installed for two weeks — which is why this rule stalls more launches than any bug does.
IndieAppCircle is a testing exchange between indie developers. You test other people's Android apps to earn credits, then spend them to get other developers into your closed test. They own real devices, they already know what closed testing is, and many of them need the same 14 days from you.
"Finally a place where other devs give real feedback instead of generic compliments."
"The credit system is brilliant. The more I help out others, the more they help me in return."
What Google actually requires
Three conditions hide in one sentence, and all three have to hold at once. Full detail in the guide to the 12 testers, 14 days rule.
12 opted-in testers
Invited does not count. Twelve people have to accept and join the closed test. It was 20 until December 2024, and it is a minimum, not a target.
14 continuous days
Consecutive, per tester. A tester who uninstalls in week two stops counting, and the count has to hold at 12 or more every single day.
Usage that looks real
Hitting the numbers makes you eligible to apply. The application then asks whether testers used the features and behaved like real users. A timer does not pass.
How to get your 12 testers on IndieAppCircle
There is no special closed-testing mode. The normal submission form already has everything a closed test needs — a link, instructions, a reward, and a platform tag.
Test a few Android apps to earn credits
Browse the Android apps currently looking for testers, install one, test it, and write up what you found. Each approved test pays out credits — the same credits you will spend on your own testers.
List your app with the closed-test opt-in link
Submit your app with the Play closed-testing opt-in URL (or your Google Group join link) as the app link, tag it as Android, and write test instructions that name the flows you want testers to reach.
Ask for the 14 days and pay for it
Say in the instructions that the most useful thing a tester can do is stay opted in for 14 continuous days. Set a higher reward than a one-off test so the commitment is worth it.
Approve tests and collect the feedback
Testers join through your opt-in link, use the app, and submit written feedback. Approve each test to pay them. Keep the notes — you describe the closed test in your own words when you apply for production access.
Why other developers are the right testers for this
Every usual source of testers has a catch that shows up somewhere in the 14 days.
Friends and family are willing, but half of them are on iPhones and their feedback is too polite to quote.
Reddit and Discord have reach, but most communities are tired of closed-testing requests and several ban them. Drop-off in week two is high.
Paid tester groups are fast, and the downside is not a rejection — it is account termination when the accounts share device fingerprints and never open the app. Why buying testers backfires.
Other indie developers own Android devices, do not need the requirement explained, are not surprised by a rough build, and write feedback because they build software themselves.
The exchange is symmetrical
Nobody here is a paid account. Every tester is a developer who wants credits to get their own app tested. That is what makes the feedback written rather than silent — and written feedback is what the production access form asks you to describe.
It costs you time instead of money: you test a few apps first. Many of the Android apps in the feed are closed tests too, so you will often be giving the same two weeks you are asking for.
Make the 14 days count the first time
A closed test that passes on the first attempt usually has all of this in place before day one. Write it into your test instructions.
Tell testers, in plain language, to stay opted in for two full weeks — and that uninstalling to free up space is the one thing that breaks the test.
Name the specific flows you want reached. Testers who are told what to try cover more of the app than testers told to have a look around.
Ship one update mid-test and tell testers what changed. It gives them a reason to reopen the app and gives you something concrete for the application.
Keep notes as feedback comes in: what was reported, what you changed, which features nobody reached. You will need specifics on the form.
Budget three to four weeks from finished build to production. Recruiting takes days, the clock starts at the twelfth tester, and review takes up to a week.
If you were rejected once, keep the testers who are still opted in and add more. Continuity is the scarce resource; do not restart from zero.
What developers search when they hit this wall
If any of these is how you got here, this page is the answer to it.
FAQ
The questions developers ask most in the two weeks between a finished build and production access.
Who does the 12 testers rule apply to?
Personal Google Play Console accounts created after 13 November 2023. If your account is older than that, or it is an organisation account, you can publish to production without a closed test.
Is it 12 testers or 20?
It is 12. The requirement launched at 20 testers in November 2023 and Google reduced it to 12 in December 2024. Plenty of older guides still say 20.
Do invited testers count, or only opted-in ones?
Only testers who accepted the invitation and joined the closed test count. Sending 30 invitations and having 8 people join is 8 testers.
What happens if a tester uninstalls the app during the 14 days?
A tester who opts out before 14 consecutive days does not count, and if they rejoin the 14 days start again for them. This is why you ask testers up front to stay opted in for two full weeks, and why you recruit more than 12.
Is using IndieAppCircle to find testers allowed by Google?
Google does not restrict how you recruit testers. What it forbids is fake engagement: bots, emulators, install farms and accounts that never open the app. Testers here are real developers on their own Android devices, testing your app because they want the credits to get their own app tested.
Does it cost money?
No. You earn credits by testing other developers' apps and spend them to reward the people who test yours. New accounts start with a few credits, and there is nothing to buy to get through a closed test.
Will testers really stay opted in for 14 days?
Most will if you ask, because many of them are stuck behind the same requirement. Put the two-week ask in your test instructions and set a higher reward to match the longer commitment. Testers who just try the app once and uninstall are the default everywhere else — here you can say what you need.
I already have testers and got rejected. Does this help?
Yes, if the second attempt needs people who actually open the app more than once. Rejections after hitting the count usually mean the test did not look like real usage. Other developers leave written feedback, which is exactly the evidence the production access form asks for.
Read before you start the clock
Three guides that cover the parts of the requirement that are not obvious from the console.
The 12 testers, 14 days rule, explained
Who it applies to, what “continuous” means, and where the 14 days most often go wrong.
Hit 12 testers and still got rejected?
What the rejection messages mean, why engagement beats the count, and how to rebuild a test that passes.
Buying testers vs getting real ones
What a paid tester group actually is, the account-termination risk, and how reciprocal testing compares.
Start your closed test with real testers
Test a couple of Android apps tonight, list yours with the opt-in link, and ask for the two weeks. No fee, no bought accounts, and feedback you can quote when you apply.
Not in closed testing, just want eyes on your build? The Android app feedback page covers pre-release testing without the 14-day requirement. Building with Flutter or React Native? There are pages for Flutter apps and React Native apps too.