Google Play's 12 testers, 14 days rule: a step-by-step guide (2026)

If you opened a personal Google Play Console account after 13 November 2023, the Production button stays locked until you run a closed test. This guide explains the rule in plain language, shows how Google counts your testers, lists every question in the production application and gives you a 14-day plan that produces the kind of testing Google wants to see.

Who the rule applies to

• Personal developer accounts created after 13 November 2023. Until you meet the requirement, Production and pre-registration are disabled.
• The requirement started at 20 testers and was lowered to 12 in December 2024. The 14-day period did not change, so guides that still say “20 testers” are out of date.
• Google's help page describes the requirement for personal accounts. Organization accounts are verified differently (for example with a D-U-N-S number) — see personal vs. organization accounts.

How Google counts your testers

This is where most developers get caught out. Google does not count downloads; it counts testers who are opted in to your closed test — people who accepted your invitation through the opt-in link.

• Every tester has their own 14-day clock. Someone who leaves on day 10 doesn't count, and if they opt out and back in, their 14 days start again.
• A replacement starts from zero. If one of your 12 leaves, the person who replaces them needs a full 14 days of their own — so you can't apply until 12 people have each been in for 14 unbroken days.
• Recruit a buffer. Inviting 15–20 people means one or two dropping out doesn't push your application back by two weeks.
• Opted in is not the same as engaged. A tester who joins and never opens your app still counts towards 12, but adds nothing to the testing Google asks you about later.

Step by step: setting up the closed test

1. In Play Console, open Closed testing and create a release: upload your app bundle (.aab) and add release notes.
2. Add your testers with an email list or a Google Group. Each tester needs a Google account, and the address you add must be the one they use on Google Play.
3. Check the track's countries / regions so that every tester's country is included.
4. Send the release for review. Closed test releases are reviewed too, so allow some time before testers can install.
5. Share the opt-in link (web link). Testers open it, accept the invitation, then install the app from Google Play.
6. Keep at least 12 testers opted in for 14 days. Collect feedback, fix problems and ship updates during the test.
7. When the requirement is met, open the Dashboard and click Apply for production.

Need more detail on tester lists, Google Groups and why testers sometimes can't join? See our closed test setup guide.

The 9 questions in the production application

The application has three parts. Your answers are saved only when you click Next (parts 1 and 2) or Apply (part 3), so write your answers somewhere first.

Part 1 — About your closed test

1. How easy was it to recruit testers for your app?
2. How engaged were your testers — did they use all the features you wanted to test?
3. How did tester usage compare with what you expect in production, and what differences did you notice?
4. A summary of the feedback you received and how you collected it.

Part 2 — About your app or game

1. Who is the intended audience? Be as specific as possible.
2. How does your app provide value to users (or what makes your game unique)?
3. How many installs do you expect in your first year?

Part 3 — About your production readiness

1. What changes did you make based on what you learned in the closed test?
2. How did you decide that your app is ready for production?

Notice what Google is asking: engagement, feedback and changes you made because of it. Twelve names on a list cannot answer these questions — real use during the test can. See example answers to all 9 questions.

Why apps get rejected: “Testers were not engaged”

Meeting the numbers is not the finish line. Developers who are refused production access get an email saying their app isn't ready for production yet, with reasons such as:

• “Testers were not engaged with your app during your closed test”
• “You didn't follow testing best practices, which may include gathering and acting on user feedback through updates to your app”
• “Your answers to the application questions about your app, closed test, or production readiness were incomplete or insufficient”

Google doesn't publish an exact engagement threshold. What it does tell you is to give testers clear instructions, encourage them to use as many features as possible, keep a record of their feedback and act on it. Its help page also lists policy problems, crashes, broken features and missing test login details (for apps that need an account) as things that delay or block approval.

If you're rejected, you'll need to keep testing: developers who have shared their rejection emails report being asked for another 14 days of closed testing with engaged testers before applying again. Use that time to fix what went wrong, not just to wait. Our guide to what “testers were not engaged” means has a step-by-step plan.

A 14-day plan that produces real engagement

This is our suggested plan, not a Google requirement. The idea is simple: give testers a small, specific task every few days so the app is actually used across the whole period — and ship at least one update based on what they tell you. For a copy-and-use version with ready messages, see our 14-day task plan template.

Where to find 12 testers

• Friends and family — free and easy to ask, but they often install once and forget the app, which is exactly the engagement problem.
• Developer communities — Android developer forums, Discord servers and Reddit groups where people test each other's apps. Free, but nobody tracks who is really testing.
• Paid services — fast, but read what they promise carefully. Only Google decides on production access, so no one can honestly guarantee approval.
• Test-swap platforms — you test other developers' apps and they test yours. This is what we're building at SwapTesters, with daily tasks spread over the 14 days and quiet testers replaced from a waiting queue.

Frequently asked questions

Source: Play Console Help — App testing requirements for new personal developer accounts. We last checked this article against it on 14 October 2026. Google can change these rules, so always confirm in Play Console before you plan your launch.