In this guide
Some new developer accounts must run a closed test before they can publish to production. Here is what the official help page says, and what to do with it.
Requirement box
| Item | Rule (per Google) |
|---|---|
| Who | "personal developer accounts created after November 13, 2023" |
| Testers | "a minimum of 12 testers" |
| Duration | "opted in continuously for at least 14 days" |
| Next step | Apply for production in the Dashboard of Play Console |
Source: Play Console Help, retrieved and verified 2026-10-17. Rules can change; re-check before you start.
What counts and what does not
- Opted in means the tester joined your closed test and stayed in. Installing alone is not the wording used.
- Continuous means no gap. A tester who joins, tests for fewer than 14 days and then opts out "do[es] not count toward the requirement", according to Google.
- If a tester leaves and comes back, Google says "the 14 days must be consecutive". See what counts as 14 days.
Organization accounts
The page I checked talks about personal accounts and does not address organization accounts. Read the current policy for your account type; see personal vs organization account.
A practical reading
- Find out if your account type and creation date fall under the rule: does your account need a closed test?
- Plan for more than 12 people, because anyone who leaves early does not count. See tester opt-out.
- Start the clock only when enough testers are really opted in.
- Apply from the Dashboard once the criteria are met.
What no guide can promise
Meeting the numbers is a requirement for applying. This page makes no promise about the outcome of the review.
How AppReviewX helps
AppReviewX test groups give you 12 testers for 14 days in a row for Android apps, with private, structured feedback. One feedback is one credit; new accounts begin with 0 credits.
Hub: Google Play closed testing. Not legal advice.