If you created a personal Google Play developer account after November 13, 2023, you cannot publish your app until you run a closed test with at least 12 testers opted in for 14 continuous days. This guide covers the Play Console setup, the mistakes that quietly reset your 14-day clock, and the real ways to find testers.
What Google actually requires
You need at least 12 testers opted in to your closed test, continuously for the last 14 days, before you can apply for production access. Twelve invites sent is not twelve testers. It means twelve unique Google accounts that opted in through your link and installed the app on a real device. Emulators, bots, and duplicate accounts do not count.
Organization accounts are exempt. Google dropped the minimum from 20 testers to 12 on December 11, 2024, but kept the 14-day window.
Only the closed track counts. Internal testing and open testing don't, and this comparison of internal, closed and open testing covers what each one is for.
Setting up closed testing in Play Console, step by step
- In Play Console, open your app and go to Test and release, then Testing, then Closed testing. Create a new closed test track.
- Upload a build to the track. Any installable version is enough to start.
- Add testers under the track's Testers tab: paste Gmail addresses or link a Google Group.
- Send testers the opt-in link Play Console generates. Each person must open it signed into their Google account, tap Join, then install from the Play Store.
- The 14-day clock starts once the track is live and at least 12 testers have opted in. It counts from the moment you cross 12.
- After 14 unbroken days at 12 or more testers, an Apply for production button appears on your dashboard.
- Google reviews the application, usually within 7 days.
The part that catches most developers: the clock resets
The 14 days must be consecutive. If a tester opts out on day 9, their days are gone; opting back in restarts them from zero. If you drop below 12 testers total, your whole window breaks. This is why recruiting friends fails so often: people uninstall, switch phones, or forget, and one dropout on day 13 pushes your launch back two weeks.
The real goal is not 12 testers. It is 12 testers who will not leave.
How long getting to 12 takes
I run a testing service (more on that below), so I have numbers. Across 112 closed tests up to October 2026, the median time to the 12th installed tester was 63.6 hours, about two and a half days. It isn't always that quick: 19 tests took more than a week. The full breakdown by month is public.
So budget three days to fill the track, then the 14 days, then up to a week of review.
Ways to find your 12 testers
- Friends and family. Free, unreliable. Works only if you can personally nag 15+ people daily.
- Swap groups on Telegram/Discord/forums. Free, slow, and feedback quality is near zero because everyone is farming opt-ins.
- Fiverr gigs. $5 to $50 for testers who opt in and vanish. Some use account patterns that look like testing farms to Google.
- A paid testing service. This is what I built TestFi for. $39.99 puts 16 real testers on your closed track, so a couple of dropouts don't sink you, and if fewer than 12 are still opted in on day 14 the re-run is free. Each tester also sends written notes on day 7 and day 14, which is the kind of evidence Google's production form asks about.
Full disclosure: TestFi is my product. The prices are public and you can check everything without talking to anyone.
FAQ
When does the 14-day clock start? Once your track is live with a build and 12+ testers have opted in. Not when you create the track.
Do testers need to open the app every day? The written rule is staying opted in for 14 continuous days. But Google's review also asks about engagement, and apps whose testers never opened them get rejected for insufficient testing.
What happens if a tester opts out? Their continuous-day count dies. Below 12 total, your window breaks and restarts.
How long does the production review take? Usually within 7 days. Budget about three weeks end to end.
Updated October 2026 with current prices and data. Originally published on the TestFi blog.
Top comments (0)