Google Play's 12-tester rule: 5 things I wish I knew before my closed test

Sabahattin Sudan — Wed, 14 Oct 2026 15:45:25 +0000

If you opened a personal Google Play developer account after November 2023, you can't publish until 12 testers have been in your closed test for 14 days in a row. I'm going through this with my own app right now, and the rule is trickier than it looks. Five things that matter:

1. Google counts opt-ins, not installs — and every tester has their own clock

If someone leaves on day 10, their replacement starts at day 0. Invite 15–20 people, not 12, so one or two dropping out doesn't push your application back by two weeks.

2. 14 days is the minimum to apply, not a guarantee

The most common rejection line developers share is: "Testers were not engaged with your app during your closed test." Twelve people who installed once and forgot the app won't cut it.

3. Ship at least one update during the test

Another rejection reason is literally: "You didn't follow testing best practices, which may include gathering and acting on user feedback through updates to your app." No update means no evidence you listened.

4. The application has 9 questions — answer them with numbers

Google asks how you recruited testers, how engaged they were, what feedback you got, what you changed and how you know the app is ready. "Testers liked it" is a weak answer. "14 of 16 testers used the main feature on at least 10 of the 14 days; version 1.0.3 fixed two crashes they reported" is a strong one. Only use real numbers.

5. Give testers tasks, not "please test my app"

A small, specific task every couple of days keeps people actually using the app across the whole 14 days — and gives you feedback to quote in the application.

I wrote the full step-by-step guide — how Google counts testers, all 9 production access questions with example answers, and what to do after a rejection — here: Google Play's 12 testers, 14 days rule: a step-by-step guide