Twelve is a floor, not a target
Google counts testers who are opted in, not testers you invited. Eleven on day thirteen is not eleven-twelfths of a pass — it is a fail, and the fortnight starts again.
For Google Play personal developer accounts
Real testers for your Play Store closed test
Google will not let a personal developer account publish until twelve testers have stayed opted in for fourteen continuous days. Finding twelve people who will actually stay is the part nobody warns you about. We supply them, watch for drop-outs, and hand you the proof.
Pay per run with card or M-Pesa. No subscription, nothing renews.
Why your app is stuck in closed testing
The fourteen days must be continuous
A tester who uninstalls or leaves the group breaks the run. Nobody tells you; you simply find the button still greyed out when you go to apply.
Friends and family run out
Most developers reach seven or eight from people they know, then stall. The remaining places are the ones that cost weeks.
How it works
- 1
Add your app
Package name and the closed-test opt-in link from Play Console. Two fields.
- 2
Choose a run
Twelve testers for the requirement, or more if you want a margin against drop-outs.
- 3
Testers opt in
Usually within hours. You watch each one join, screenshot and all.
- 4
Fourteen days pass
Anyone who drops out is replaced the same day, so the clock never quietly resets.
And when you want to know what actually breaks
Compliance gets you published. It does not tell you that your sign-up screen fails on a three-year-old Android, or that the payment sheet is unreadable in Swahili. A QA run puts testers on the app with a brief, and you get written reports — steps, device, severity, screenshots — instead of a star rating and a shrug.
- Reports you can paste straight into an issue tracker
- Real devices, named — model and Android version on every finding
- Severity you can plan around: blocker, major, minor, cosmetic
- A retest after you ship the fix
Questions developers ask
- Why does Google Play need 12 testers for 14 days?
- Since 2023, a personal Google Play developer account must run a closed test with at least 12 testers who stay opted in for 14 continuous days before it can apply for production access. The count is of testers still opted in — if someone leaves on day 10, the clock does not simply carry on.
- Are these real people or bots?
- Real people with real Google accounts and real devices. Bots cannot opt into a closed test, and Google can tell. Every tester on PlayAppTest has a verified Play account and confirms their opt-in with a screenshot you can keep.
- What happens if a tester drops out?
- We replace them and tell you the same day. Because the 14 days count continuous opt-in, a silent drop-out is the one thing that quietly costs you a fortnight — so we watch for it rather than leaving you to discover it at the end.
- How long does it take to start?
- Testers are usually assigned within a few hours of payment, and your 14 days begin the moment the last one opts in. You can watch each tester join from your dashboard.
- Can you test iOS apps too?
- Yes, through QA runs — testers install a TestFlight build and report what breaks. The 14-day rule is a Google Play requirement and does not apply to the App Store.
- How do I pay?
- Card or M-Pesa, through Paystack. You pay per testing run — there is no subscription, and nothing renews on you.
Get the fourteen days behind you
Add your app, pick a run, and watch the testers arrive. Most runs have their full twelve within a day.
Create an account