Day15 › Guides

12 testers for 14 days: Google Play’s closed testing requirement, explained

Checked against Google’s Play Console Help on Oct 29, 2026 · By Anchor Point Apps

If you registered a personal Google Play developer account recently, you can’t publish to production straight away. Here is exactly what Google requires, based on its help documentation.

The rule

Google’s article says developers with personal accounts created after November 13, 2023 “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.” When you meet this, you can apply for production access from the Dashboard in Play Console. Until then, features such as Production and Pre-registration stay disabled.

The article describes the requirement for personal accounts. Your Play Console Dashboard shows what applies to your account; we haven’t seen Google describe this requirement for other account types, so check there rather than assuming.

What “continuously opted in” means

• At the time you apply, at least 12 testers must be opted in to your closed test, and they must have been opted in continuously for the preceding 14 days.
• Testers who opt in, test for fewer than 14 days, then opt out don’t count.
• If a tester opts out and later opts back in, the 14 days must be consecutive to count.

The order of steps

1. Complete your app setup. Closed testing becomes available after setup (the Dashboard walks you through it). Internal testing, by contrast, needs no setup and is optional but recommended as a starting point.
2. Create a closed test release and upload your app bundle. After you publish a test for the first time, Google says the test link “can take several hours to become available to testers.”
3. Add testers by email list (you can create up to 200 lists of up to 2,000 users each, up to 50 lists per track) or by Google Group. Add a feedback email or URL, then copy the shareable opt-in link.
4. Get 12+ people to opt in via the link, and tell them to stay opted in. Google’s own advice: “Inform your testers that they need to remain opted in to your closed test continuously for at least 14 days.”
5. Collect feedback and ship fixes during the test.
6. Apply for production: Dashboard › Apply for production, then complete three sections: About your closed test, About your app/game, About your production readiness. See how to prepare those answers.
7. Wait for the review. Google says it usually takes seven days or less. The account owner is notified by email.

Planning the calendar

Our advice: the 14 days are a minimum, and they only start counting once enough testers are actually opted in. Recruiting, the first-publish delay, and review time all sit on either side. Starting recruitment before your closed test is live (so you have names ready to send the link to) is the cheapest way to avoid wasting days.

Common ways people lose days

• Exactly 12 testers, then one opts out → the streak problem.
• Testers can’t find the app or the link doesn’t work → opt-in link troubleshooting.
• Applying, then hearing back that more testing is required.