Skip to content

Google Play testing requirements

Who needs Google Play’s closed-testing requirement before production?

Personal Play Console accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for the 14 days before applying for production access (Google Play Console Help, checked November 18, 2026). This page explains who is affected, what continuous opt-in means, and what to prepare before you apply.

  • Who the rule applies to
  • What counts in Play Console
  • How to apply after day 14

Educational guide · Verified against Google Play Console Help · Updated November 19, 2026

Diagram: at least 12 testers opted in every day for 14 days in a row, for personal accounts created after 13 November 2023, then apply for production access
12 testers × 14 daysthe qualifying closed-testing minimum

Does this apply to you?

Personal Play Console account created after November 13, 2023?

Yes Run a qualifying closed test before Production unlocks.

12 testersminimum opted in
14 dayscontinuous preceding window
Closed testthe track that qualifies
Nov 13, 2023personal-account cutoff

No Organization account or older personal account

Google's help doesn't describe the requirement for these accounts. Check your Play Console Dashboard: it shows whether the closed-test step applies.

The short answer

The requirement in plain English

If your personal Play Console account was created after November 13, 2023, your app must complete a qualifying closed test before the Production and Pre-registration features become available. At least 12 testers must be opted in when you apply, and they must have remained opted in continuously for the previous 14 days.

That threshold makes you eligible to submit the production-access form; it is not automatic approval. Google also asks how you recruited testers, what they used, what feedback you received, what changed, and why the current build is ready.

Before you apply

Confirm these six items before you request production access

The release is available on a closed testing track—not only internal testing

At least 12 testers are still opted in after 14 continuous days

Tester accounts, countries and devices can access the Play Store test listing

You recorded realistic usage, feedback, fixes and retest results

Login, onboarding and the app's core task work on the current build

Store listing, privacy policy, Data safety and reviewer access are accurate

Play Console Production page: apply for production access stays locked until the closed test runs with at least 12 testers for at least 14 days

Official rule

Who must complete the closed test?

Google's published requirement covers personal Play Console accounts created after November 13, 2023. These accounts must complete a qualifying closed test before Production and Pre-registration become available.

  • Personal account: The requirement applies to personal Play Console accounts created after November 13, 2023.
  • 12 opted-in testers: At least 12 testers must be opted in to the qualifying closed test when you apply.
  • 14 continuous days: The same qualifying minimum must cover the preceding 14 days continuously.
  • Application, not approval: Meeting the threshold unlocks the production-access application. Google still reviews your app and answers.
Read the official Google requirement

What counts

Closed testing is not the same as internal testing or a direct install

MethodWhat it is forCounts toward 12 × 14?
Internal testingFast smoke tests with a small trusted group; available before full app setup.No — useful for QA, but it does not satisfy this production-access gate.
Closed testingA controlled group invited by email list or Google Group after app setup is complete.Yes — this is the qualifying track for affected personal accounts.
Open testingA public beta that anyone can join and send private feedback from.Not for this gate — it becomes available after production access.
Sideloaded APK/AABDirect installs outside the Play Store testing flow.No — these installs do not create a qualifying Play Console opt-in.
Compare internal vs closed testing

Play Console setup

How to meet the Google Play testing requirements step by step

01

Prepare

Complete app setup and test the build internally

Finish the store listing, app content, Data safety, target audience, app access and policy declarations. Use internal testing for fast smoke tests, then fix install, login and first-run blockers before recruiting a larger group.
02

Launch

Create the closed track and publish a stable release

In Play Console, open Testing → Closed testing, create or select a track, upload the AAB and roll out the release. Add testers by email list or Google Group, provide a feedback channel and copy the official opt-in link.
03

Opt in

Confirm 12 or more completed opt-ins

An invitation is not an opt-in. Each person must accept the test with an eligible Google account and install through Google Play. Use Play Console—not a spreadsheet or chat reply—to confirm the qualifying count.
04

14 days

Keep the window continuous and collect useful evidence

Monitor opt-ins, give testers realistic feature tasks, review crashes and feedback, fix important issues and retest changes. Keep a dated record of what happened so the production-access answers reflect the real test.
05

Apply

Verify eligibility and request production access

After Play Console confirms the qualifying window, open the Dashboard and select Apply for production. Answer the three sections in your own words, keep the closed test active during review and respond if Google requests more testing.
TestMyApps run dashboard at day 16 of 16 with 14 of 14 testers assigned and tester reports tracked
Keep the count, testing tasks, feedback and fixes visible throughout the full window.

Practical timeline

When the 14-day testing window starts—and what to do during it

Do not count from the AAB upload. Use a conservative day zero: the closed release is available and tester number 12 has completed opt-in. Play Console is the source of truth for eligibility. If opt-ins are stuck, see how to invite testers.

View the testing timeline
  1. 1

    Before day 0

    Finish setup and publish the closed release

    Complete app content, store listing, Data safety, target audience, app access and policy declarations. Upload a stable AAB, create the closed track and roll out the release.
  2. 2

    Day 0

    Confirm the twelfth opt-in

    Share the official opt-in link. Each tester must use an eligible Google account, accept the test and install through Google Play. Start counting only after the release is available and 12 testers are confirmed.
  3. 3

    Days 1–3

    Find access and first-run blockers

    Prioritize installation, onboarding, login, permissions and the app's main task. Record device, Android version and build number with every issue.
  4. 4

    Days 4–13

    Broaden coverage and retest fixes

    Ask testers to exercise important features, edge cases and realistic flows. Monitor the opted-in count, review Play Console feedback, crashes and ANRs, and verify each meaningful fix.
  5. 5

    Day 14+

    Verify eligibility before applying

    Use the status in Play Console as the source of truth. Confirm the continuous window, summarize recruitment and feedback, and recheck the current build, policies and reviewer access.

Want the testing window managed? TestMyApps coordinates real testers, monitors opt-ins and provides a closeout report.

Compare plans

Requirements guide

Organization accounts

Google Play Console Help (checked November 18, 2026) describes this testing requirement for personal developer accounts created after November 13, 2023. It does not describe the requirement for organization accounts. Organization accounts are meant for businesses and other organizations, and Google asks for a D-U-N-S number to verify the organization when the account is created.

If you publish on behalf of a registered business, Google's account-type guidance points you to an organization account, and some app categories, such as financial services, health and government apps, require one. Check your own Play Console Dashboard: it shows whether the closed-test step applies before Production unlocks.

Requirements guide

What continuous opt-in actually means

Google describes the requirement as at least 12 testers opted in continuously for the preceding 14 days when you apply. A person who joins for a few days and then opts out does not complete the requirement. If they later rejoin, their individual continuous period starts again.

The safest operational plan is to recruit more than the minimum and begin the calendar only after the release is available and the twelfth opt-in is visible. Continue checking the count through the application date instead of assuming that everyone who joined once is still eligible.

  • Use the closed-track status in Play Console as the source of truth
  • Keep a buffer above 12 so a single access problem does not threaten the run
  • Tell testers clearly that they must remain opted in for the full period

Requirements guide

How to recruit testers and give them meaningful tasks

Google recommends recruiting people who resemble the intended audience and giving them clear instructions. Friends, colleagues, customers, relevant communities and managed testing services can all be sources; what matters is that people can access the release, exercise the product and provide feedback you can describe honestly.

Write a short testing brief that covers install and first launch, onboarding, account creation, the main value flow, payments or subscriptions where relevant, notifications, permissions, offline behavior and recovery from errors. Ask for device model, Android version, app version and steps to reproduce with each issue.

  • Create one clear feedback channel and show testers what useful bug reports contain
  • Prioritize realistic user journeys instead of asking people only to open the app
  • Track which issues were fixed, which build contains the change and who retested it

Requirements guide

Testing requirements are only one part of production readiness

A healthy tester count does not compensate for a broken or non-compliant app. Before you apply, check crashes and ANRs, run the pre-launch report, verify all reviewer credentials, and confirm that the store listing and disclosures match the behavior of the current release.

Google says production review is not a troubleshooting step. Treat the closed test as a release-quality checkpoint: fix the issues most likely to block a new user, retest those flows and document remaining risks rather than claiming the app is perfect.

Requirements guide

How to write stronger production-access answers

Write specific, evidence-based answers. Explain where testers came from, which scenarios they completed, what usage differed from your expectations, the main feedback themes and the improvements that followed. A short factual answer is stronger than a long generic claim.

For production readiness, connect decisions to evidence: crash-free sessions improved after a fix, a confusing onboarding step was rewritten and retested, or test credentials and policy declarations were verified against the release candidate. Never copy another app's answers or invent activity that did not happen.

Requirements guide

When managed closed testing is useful

Self-managed testing can work when you already have an engaged audience and time to coordinate it. Managed help is useful when recruitment, opt-in troubleshooting and daily continuity checks are the main blockers—not when the build itself still needs basic QA.

TestMyApps coordinates real testers and the testing window, while you remain responsible for the app, policies, fixes and answers submitted to Google. No testing service can sell or guarantee production access because Google makes the final decision.

After the test

What Google asks when you apply for production access

Completing the 12-testers-for-14-days threshold makes you eligible to apply. It does not guarantee approval. Google asks about the test, the product and why the current build is ready for a broader audience.

Part 1

About your closed test

Explain how testers were recruited, which features they used, whether behavior matched your expected audience, what feedback you received and how you collected it.

Part 2

About your app or game

Describe the intended audience, the value your product provides and a realistic estimate of first-year installs.

Part 3

About production readiness

Connect specific test findings to the changes you made, then explain the evidence you used to decide that the current release is ready.

Read the production-access application guide

Avoid a reset or weak application

Common mistakes that delay production access

Most delays come from starting the clock too early, confusing an invitation with an opt-in, or reaching day 14 without credible notes about what was tested and improved.

01

Counting from the upload date instead of the date the release is available and the twelfth tester has opted in.

02

Adding an email to a list but never confirming that the person accepted the test with the same Google account used in the Play Store.

03

Recruiting exactly 12 people with no buffer for an incompatible device, country restriction or accidental opt-out.

04

Using internal testing time, sideloaded builds or chat confirmations as proof of a qualifying closed-test window.

05

Collecting no structured feedback, shipping no verified fixes, and then writing generic answers in the production-access form.

06

Applying with broken login credentials, policy mismatches, crashes or a store listing that no longer matches the build.

Review common Google Play policy rejection reasons and fixes

Optional managed help

Eligible but short on reliable testers?

If your account needs a qualifying closed test, TestMyApps coordinates real testers, monitors opt-ins, and provides a closeout report while you focus on product fixes and the production-access answers.

Get 12 testers for 14 days

FAQ

Google Play testing requirement questions

Plain-English answers to the questions developers ask before and during a qualifying closed test.

What are the Google Play testing requirements for new personal accounts?

Personal Play Console accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in continuously for the preceding 14 days before applying for production access.

When does the Google Play 14-day testing period start?

Use the date when your closed release is available and at least 12 testers have completed opt-in. Uploading an AAB, creating a tester list or sending invitations does not by itself start a qualifying window.

Does internal testing count toward the 12 testers for 14 days requirement?

No. Internal testing is recommended for early QA, but the production-access requirement for affected personal accounts must be completed on a closed testing track.

Does adding 12 email addresses mean I have 12 testers?

No. Adding someone to an email list or Google Group only makes them eligible. Each person must open the official link, accept the test with the correct Google account and remain opted in.

What happens if a tester opts out during the 14 days?

A tester who opts out before completing 14 continuous days does not count. If they opt back in, their continuous period starts again. Maintain a buffer above 12 and monitor the Play Console count throughout the run.

Do testers need to use the app every day?

Google's published numeric threshold is continuous opt-in, but its guidance also emphasizes meaningful tester engagement, feedback and improvements. Give testers realistic tasks across the window and describe actual activity honestly in your application.

Can I use friends, family or a Google Group as testers?

Yes, provided they use eligible Google accounts, join through the closed-test flow, can install the release and remain opted in. Recruit people who can realistically use the app and provide useful feedback.

Does completing closed testing guarantee production access?

No. It makes an affected account eligible to apply. Google still reviews the testing answers, app quality, policy compliance, store information and production readiness, and may request more testing.

How long does Google take to review a production-access application?

Google says review usually takes seven days or less, although it can take longer. Keep the closed test active and continue addressing important issues while you wait.

Can TestMyApps help with the closed-testing requirement?

Yes. TestMyApps offers managed tester coordination, opt-in monitoring and closeout reporting. You remain responsible for app quality, policy compliance and the answers you submit, and Google makes the final production-access decision.

Sources and next steps

Official Google guidance and useful TestMyApps resources

Google Play Console HelpApp testing requirements for new personal developer accountsFirst-party reference used to verify this guide.
Google Play Console HelpSet up an open, closed, or internal testFirst-party reference used to verify this guide.
Google Play Console HelpChoose a developer account typeFirst-party reference used to verify this guide.