Google Play's closed test: 12 testers for 14 days

What the rule says

A personal developer account created after 13 November 2023 may only publish an app to production after running a closed test with at least 12 testers for at least 14 consecutive days.

It is not a review queue. It is a fixed duration, and no amount of urgency shortens it.

The three things that freeze the count

A tester who did not accept the invitation. Being on the list is not enough: the person has to open the link, accept and install. The console shows how many accepted, and that is the number that counts.

Somebody uninstalling midway. If the total drops below 12, the count stops until you replace them. Invite 15 or 16, not exactly 12.

Assuming the clock starts when the test is created. It starts when the 12 are in.

How not to lose a fortnight

1. Decide the account type before creating it. If you have a registered company, an organisation account skips this entirely. It is the only way to avoid the wait, and it cannot be changed later without opening another account.
2. Start the test early. It runs in parallel with everything else: listing, screenshots, privacy policy, data form. Do not wait for the app to be finished before starting the 14 days.
3. Invite with slack. Fifteen people to guarantee twelve active ones.
4. Publish on the web meanwhile. A browser-installable app goes through none of this and is live today. Two weeks of waiting need not be two weeks without a product.

The short version

• it applies to personal accounts created after 13 Nov 2023;
• 12 Google accounts accepted and active, for 14 consecutive days;
• the count starts when all 12 are in, and freezes if it drops below;
• organisation accounts skip the rule, and that is the decision to make before creating the account;
• publish on the web while the clock runs.

The full process is in publishing an app to Google Play.