Quick answer
The 14 days must be continuous with at least 12 testers opted in. If your opted-in count drops below 12 at any point — someone opts out, leaves your Google Group or is removed from the list — the continuous period is broken and counting effectively starts again. Recruit a buffer of extra testers and don't change your tester lists mid-test.
How the count works
The requirement in Google's Play Console Help page on app testing requirements is at least 12 testers who have been opted in for at least the last 14 days continuously. That wording matters. It is not "12 testers at some point" or "12 testers on day 14". If the number of continuously opted-in testers falls below 12, you no longer have 14 unbroken days behind you.
Common causes of a reset
| Cause | How it happens | Prevention |
|---|---|---|
| Tester opts out | A tester taps "Leave the program" or loses interest | Recruit 15–20, not exactly 12 |
| Group or list edits | You remove a person, swap the email list or change the Google Group | Freeze tester lists once the test starts |
| Wrong Google account | Tester opted in with a different account than the one on your list | Ask testers to confirm the exact email before opting in |
| Track changes | Creating a new closed track and moving testers to it | Keep the same track; just upload new builds to it |
| Tester exchange drop-offs | "Test for test" partners stop after a few days | Use committed testers with daily tasks |
Updating your app does not reset the count
Uploading new builds to the same closed track is normal and expected — that is what testing is for. Fix bugs and push updates during the test. What matters is the testers staying opted in, not the build staying the same.
A buffer plan that works
- Recruit 15–20 testers so a few drop-offs don't matter.
- Collect each tester's exact Google account email before day 1.
- Use one closed track and one tester list or Google Group for the whole test.
- Give testers a short daily task (5–10 minutes) so they stay involved.
- Check the opted-in count every day and follow up immediately if it drops.
- Log start date and progress — our closed testing tracker does the date maths for you.
If it has already reset
- Find out why: check who left and whether any list or group changed.
- Top up to well above 12 testers straight away.
- Count 14 days from when you are safely back above 12.
- Use the extra days well: more testing gives you better answers when you apply for production access.
If recruiting and keeping testers is the problem, our Google Play Closed Testing service runs multi-day campaigns with eligible testers and daily check-ins. Approval always remains Google's decision.
Frequently asked questions
Does removing one extra tester reset the clock?
Only if it takes you below 12 continuously opted-in testers. That is why a buffer of extra testers is so useful.
Where can I see my opted-in tester count?
Play Console shows your closed test details and your progress toward the testing requirement on the Dashboard. Check it daily during the test.
Can I add new testers during the test?
Yes. Adding testers is fine. New testers only count toward the 14 days from when they opted in, so add them early.