Google Play closed testing
Get 12 testers for 14 days—without chasing people.
We assign 14 real Android testers for 16 days, monitor the run, replace dropouts, and give you a closeout report.
- One-time payment
- No subscription
- Free retest guarantee
Proof, not promises
A managed run you can actually see.
Clear numbers, real app examples, and a report you can use when you apply.
Across 400+ published apps. Google still makes the final decision.
Once your closed release and opt-in link are ready.
14testers
×16days
Above Google’s 12 testers for 14 days minimum.
See what your final report looks like.
Download sample reportApproval rate is our historical track record, not a guarantee for an individual app.
Everything you need
More cover. Less chasing.
We stay above Google’s minimum so your test is easier to manage from day one.
14 real testers
Two extra testers above Google’s minimum, all on physical Android phones.
16-day coverage
Two buffer days beyond the required 14-day continuous window.
Daily monitoring
We check participation and act quickly if a tester drops out.
Closeout report
Clear run details to help with your production-access application.
How it works
Three steps. We handle the middle one.
Send your opt-in link
Create your closed-testing release and share the Join on the web link with us.
We run the test
14 testers join, install, and stay opted in while we monitor the 16-day window.
Apply for production
Use your closeout report to complete Google’s production-access questions.
Usually starts in about 6 hours. Your build and opt-in link need to be ready first.
Google Play requirement
Why the 12-testers-for-14-days rule blocks so many launches
The rule sounds simple, but the details break most self-managed runs: testers must join through the official Play Console opt-in flow and stay opted in for the preceding 14 days continuously. TestMyApps also uses real people, Google accounts, and physical Android devices so testing produces useful launch feedback rather than an empty count.
Recruiting friends and strangers from Telegram or Reddit usually produces exactly that failure: people install once, never open the app again, or opt out mid-window. TestMyApps replaces that gamble with verified testers whose participation is managed end to end.
What Google actually counts toward the requirement
- At least 12 unique testers opted in through your closed testing link
- Opt-in maintained for the last 14 days continuously when you apply
- A valid closed-test opt-in recorded in Play Console for each participant
- The closed testing track — internal and open testing do not count
- Meaningful engagement Google can see when reviewing your application
Protect your testing window
The details that make 12 testers for 14 days work.
Short answers to the parts that most often delay a Google Play launch.
Who needs 12 testers for 14 days
The requirement applies to personal Google Play developer accounts created after November 13, 2023. Organization accounts and older personal accounts are exempt.
If you registered a new personal account to ship your first Android app, there is no way around the rule: the Apply for production button only appears after Play Console verifies 12 opted-in testers across the last 14 continuous days.
Why runs fail — and how a managed run prevents it
Most failed runs are operational, not technical. A tester accepts the invite with one Google account but installs with another, so the opt-in never registers. Someone opts out on day 11 and the count drops to 11, breaking the continuous window. Or the group installs once and never opens the app, which weakens the production access review even if the count technically holds.
TestMyApps removes each of those failure modes: verified testers who know the opt-in flow, daily count monitoring with buffer capacity, and engagement tasks so activity looks like real usage — because it is.
- Verified opt-ins with the same Google account used for install
- Daily monitoring so the count never silently drops below 12
- Buffer testers ready to replace any dropout immediately
- Structured usage tasks that generate credible engagement signals
After the 14 days: the production access application
Completing the window unlocks the application, not automatic approval. Google asks how you recruited testers, what feedback you collected, what you changed, and why the app is ready. Vague answers are a common rejection reason.
Every TestMyApps run closes with a report of tester participation and feedback, so you can answer with specifics — real numbers, real issues found, real fixes shipped — instead of generic filler.
DIY recruiting vs a managed run
Free routes exist: friends and family, developer communities, tester-swap groups. They can work if you have the patience to chase 15+ people daily for two weeks and restart when someone drops. The hidden cost is time — every broken window adds 14+ days to your launch.
A managed run trades a small fee for a predictable timeline. If your launch date matters, that trade usually pays for itself the first time a volunteer tester silently opts out.
Our guarantee
Free retest. Then a refund if it still isn’t approved.
We guarantee the managed testing work—not Google’s final decision.
Quick answers
Still deciding?
Here are the essentials. The detailed guides are there if you need them.
Download a sample reportHow do I get 12 testers for 14 days on Google Play?
You need 12 people opted in to your closed test continuously for 14 days. You can recruit them yourself, trade in swap groups, or use a service. With TestMyApps, you send your opt-in link and 14 testers on real Android phones join within 6 hours and stay for 16 days.
Does the 12 testers rule apply to my account?
It applies to personal developer accounts created after November 13, 2023. Organization accounts aren't held to it. Older personal accounts aren't either.
How many testers does Google Play require for closed testing?
12 testers who stay opted in to your closed test for 14 days in a row. That's the current rule for personal developer accounts created after November 13, 2023. TestMyApps runs 14 testers for 16 days so one dropout doesn't reset your clock.
Does internal testing count?
No. Only the closed testing track counts toward the requirement.
Why 14 testers and 16 days instead of 12 and 14?
Margin. If one or two testers drop late in the test, you're still at 12 or more. The two extra days mean you're not applying on the last possible hour.
What happens if a tester drops out?
I check opt-in status every day and replace dropouts. The 2 spare testers cover anyone who drops too late for a replacement to finish 14 days.
How fast do testers join?
Within 6 hours of you sending your closed testing opt-in link, as long as your closed release is rolled out.
Are the testers real people?
Yes. Real people using their own physical Android phones. No emulators.
Keep going
Guides for your next step.
Setup, tracks, and troubleshooting for Google Play closed testing.
Timeline estimatorEstimate when your 14-day opt-in window completes.
Full pricing pageCompare credit packages for managed closed-testing runs.
Free community testingRecruit volunteer Android testers in the public TestMyApps community at no cost.
Ready when your app is
Start your 14-day closed test.
14 testers. 16 days. Daily monitoring. One clear report.
