Does Google Play closed testing have to be 14 consecutive days?

Yes. The requirement is 14 continuous days, not 14 days spread across a month.

For covered personal developer accounts, Google requires at least 12 testers who have opted in to a closed test for at least 14 continuous days. The word "continuous" is doing real work in that sentence.

That does not mean the whole group must opt in at the same second. It means each tester's participation has to run without a break long enough to reset their own clock. The group also needs to stay at or above 12 eligible testers.

What breaks continuity

The common risks are:

• A tester opts out and later opts back in. Their clock restarts.
• A tester is removed from the list and re-added. Treat it as a new opt-in.
• A tester switches to a different Google account. The new account has its own clock.
• The group drops below 12 for long enough that the Console no longer sees a qualifying set.
• The closed track is deleted or replaced.

A normal app update is not on that list. Shipping a new build during the window does not reset the 14 days. You can fix bugs and keep testing.

What about weekends and holidays?

The 14 days are calendar days. Weekends count. Public holidays count. Google does not pause the clock for your team's schedule.

This is one reason a 16-day managed window is common: the extra two days absorb a late start, a replacement, or a public holiday without turning the whole plan into a scramble.

What about replacing a tester?

Replacing a tester is allowed. The replacement does not inherit the old tester's days.

If someone leaves on day 10, the new tester starts at day zero when they opt in. If you still have 12 other eligible testers, the group may remain compliant. If the departure took you to 11, you need to wait for enough replacements to complete their own 14 days.

This is why a buffer matters. Start with 14 or 15 testers when you can.

Does the test have to be active every day?

Yes. The closed test should remain active with the required testers opted in. You do not need a new build every day, and testers do not need to open the app every day. But the track needs to stay live and the group needs to remain eligible.

Pausing the track, removing the release, or letting the test lapse can interrupt the window. If you need to pause for a technical reason, fix it quickly and check the Console before assuming the days still count.

How to prove continuity

Keep a simple tracker with:

• tester name;
• Google account used;
• opt-in date;
• device;
• status;
• date removed, if any.

The Console is the source of truth, but your tracker helps you explain gaps and answer production-access questions. It also makes a replacement decision much less emotional.

The short version

• The requirement is 14 continuous days, not 14 total days.
• Each tester has their own clock.
• A normal app update does not reset the clock.
• Removing and re-adding a tester does.
• Weekends and holidays count.
• Keep a buffer and replace drop-offs early.

Next: when does the 14-day clock start? or how to replace a tester without breaking the window.