How the 14 days of Google Play closed testing are counted

The 14 days are not a timer on your app. They are counted per tester. When you apply for production access, at least 12 testers must be opted in, and each of them must have stayed opted in, without a break, for the preceding 14 days. A tester who leaves and comes back starts over.

Everything below comes back to that sentence.

What Google actually says

From the Play Console Help page on testing requirements:

• New personal accounts "must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days."
• "At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days."
• "Testers who opt in, test for fewer than 14 days, and then opt out do not count toward the requirement. If a tester opts out and opts back in later, the 14 days must be consecutive to count toward the minimum requirement of 12 continuous opted-in testers."

Three consequences:

1. The clock is per person. Testers who join on different days qualify on different days.
2. The check happens when you apply. It's a snapshot: who is opted in right now, and for how long without a break.
3. Leaving breaks the chain. There's no pause button for a tester.

A worked example

Say you publish your closed track on Monday, November 9. The opt-in link can take several hours to start working after a first publish (Play Console Help), so nobody joins that day.

On November 26 you have exactly 12 qualifying testers. That's the minimum, with zero margin.

Now imagine a second tester leaves on November 20. You're at 11. You need a new tester, and that person needs 14 days of their own. If they join on November 21, your earliest date moves to December 5. One person leaving cost you nine days.

That's why you recruit more than 12 people, and why you count opt-ins, not promises.

When to apply: leave a margin

Google doesn't define how partial days count, or which time zone it uses. Don't apply at the first possible minute.

A safe rule:

1. Find the date your 12th qualifying tester joined. In the example, November 12.
2. Add 14 days: November 26.
3. Apply one day later, and only if at least 12 testers are still opted in that morning. In the example, November 27.

Before you click Apply for production on the Dashboard, check your current tester list in Play Console. If you're at exactly 12, consider waiting until a 13th or 14th tester qualifies.

What breaks a tester's 14 days

Opting out. In the Play Store, a tester can leave a test from Manage apps & devices > Beta (Google Play Help). Once they do, their days stop counting. Tell testers up front not to leave. Google itself recommends it: "Inform your testers that they need to remain opted in to your closed test continuously for at least 14 days" (Play Console Help).

Being removed from the track. Google says a user is eligible for a test track only if they're included in the track's tester configuration and actively opted in (Play Console Help). If you remove a Google Group or an email list from the Testers tab, the people in it lose eligibility. Add testers freely during the test. Don't remove lists.

Leaving the Google Group. If your track uses a group, membership is the condition for access. A tester who leaves the group is out.

Joining your internal test. Google says a user who opts into your internal test "is no longer eligible to receive an open or closed test" (Play Console Help). Keep internal and closed testers separate. Details in Internal vs closed vs open testing.

Pausing the track. "Pause track" is how Google tells you to end a test. Testers stop receiving updates. Google doesn't say what happens to the 14-day count, so don't use it mid-test.

What doesn't break it (as far as Google says)

Publishing updates. Google encourages it: "Continue running closed tests while resolving user-reported issues and bugs. Updating your app in closed testing before releasing to production helps minimize low ratings" (Play Console Help). Nothing in Google's help says an update resets the count. Shipping fixes during the test also gives you something concrete to write in the production access form.

Adding testers. New testers start their own 14 days. They don't affect the ones already counting.

The count isn't the whole test

Meeting the numbers gets you the right to apply. It doesn't guarantee the answer. Google lists two reasons for asking you to keep testing: "having fewer than 12 opted-in testers or insufficient tester engagement during the testing period" (Play Console Help).

The form also asks whether testers used all the features, whether their usage matched what you expect in production, and what feedback they gave. Twelve people who opted in once and never opened the app give you nothing to write. Plan the 14 days so testers actually use the app, and collect their feedback as you go. The form is covered in How to apply for production access.

After you apply

Google says review "usually takes seven days or less, but can occasionally take longer", and the account owner gets an email (Play Console Help). Keep the closed test running during that time. If Google asks for more testing, testers who stayed in still count toward the next attempt.

If your tester count doesn't match what you expected, see Testers not counted. For the complete process, read the Google Play closed testing guide.