Google Play Closed Testing Requirements

Google Play closed testing requirements decide whether a new developer can publish straight away or must test first. For personal developer accounts created after November 13, 2023, Google requires a closed test with at least 12 testers opted in continuously for at least 14 days before production access. This guide covers who that applies to, how personal and organization accounts differ, and what you need in place before your test can start.

Everything here comes from Google's Play Console Help Center, mainly App testing requirements for new personal developer accounts and Choose a developer account type.

Personal vs organization developer accounts

Google Play offers two developer account types: personal and organization. Google says both have access to the same functionality, and both can monetize on Google Play using a payments profile. The difference is who the account is for and what information you provide.

Account type	Who Google says it is for	Notable requirement
Personal	Personal use, for example a student, hobbyist or amateur developer. You can still earn money and invite others to join the account.	New personal accounts (created after November 13, 2023) must meet the closed testing requirement before production.
Organization	An organization or business, for example one engaged in commercial, industrial, professional or governmental activities.	A D-U-N-S number is mandatory when providing developer account information for the organization.

When Google says to choose an organization account

Beyond the general description, Google lists types of services for which you should choose an organization account:

• Financial products and services, including but not limited to banking, loans, stock trading, investment funds, cryptocurrency software wallets and cryptocurrency exchanges.
• Health apps, such as medical apps and human subjects research apps.
• Apps approved to use the VpnService class.
• Government apps, including apps developed by or on behalf of a government agency.

The D-U-N-S number

To create a developer account for an organization, you must have a D-U-N-S number. Google describes it as a mandatory requirement when you provide developer account information for your organization or business, and says Google Play uses it to verify your identity.

Google is explicit that applying for a D-U-N-S number through Dun & Bradstreet is a completely free process, and warns developers to be aware of third-party services that may attempt to charge high administrative fees for this free registration.

Which accounts must run a closed test?

Google's testing requirements article is titled, and written, for new personal developer accounts. It states that Google Play requires personal developer accounts created after November 13, 2023 to test their apps before those apps are eligible for distribution on Google Play.

So two questions decide whether the rule applies to you: is the account a personal account, and was it created after November 13, 2023? If both answers are yes, plan for the closed test before launch. The article does not describe the same requirement for organization accounts. If you are unsure how it applies to your situation, the official article is the source to check, because Google can update it.

For the detail of the rule itself, including what “continuously” means, see our guide to 12 testers for 14 days.

What stays locked until you meet the requirement?

Google explains that certain Play Console features remain disabled for these accounts until the testing requirements are met, and names two: Production and Pre-registration. The testing tracks themselves open up in stages. Google's own summary looks like this:

Track	Purpose	Requirement to access
Internal testing	Distribute builds to a small group of trusted testers for early feedback	None
Closed testing	Share your app with a group of users you control, fix issues and check policy compliance before launch	Complete app setup
Open testing	Surface a test version on Google Play so anyone can join	Gain access to production
Production	Make your app available to users on Google Play	A closed test with at least 12 opted-in testers continuously for 14 days, then an approved application

Two consequences follow. First, an open test cannot replace the closed test for these accounts, because open testing only becomes available after production access. Second, internal testing is optional but available immediately, which makes it a reasonable place to catch obvious problems before you invite a wider closed group. Our guide to internal vs closed vs open testing compares the three tracks in detail.

What do you need before your closed test can start?

Pulling together Google's documentation, these are the things that need to be in place:

• Completed app setup. Google lists this as the requirement for access to the closed testing track.
• A release on the closed track. Google's release guide asks you to set up your store listing, prepare your app for review and configure pricing before you begin a release. On a first release you configure Play App Signing and add your app bundles.
• The right permission. To create a new release, your Play Console user needs the Release apps to testing tracks permission.
• Testers with Google accounts. Users need a Google Account or a Google Workspace account to join a test.
• A published track for the opt-in link. The opt-in link only appears once the app status is 'Published', and the first time can take several hours.
• A feedback channel. Google asks you to provide a feedback URL or email address, which appears on the tester opt-in page.

The numbers that matter

These are the figures Google publishes in the articles this guide is based on:

What	Figure
Minimum opted-in testers when you apply	12
Continuous opt-in period	At least 14 days, the 14 days before you apply
Personal accounts covered	Created after November 13, 2023
Internal test size	Up to 100 testers per app
Closed test email lists	Up to 200 lists, up to 2,000 users each, up to 50 lists per track
Production access review	Usually seven days or less, occasionally longer

Policy compliance is part of the requirement

Testing is not the only gate. Google states that it is your responsibility to make sure your app fully complies with all Google Play Developer Content Policies before you apply for production access, and that review is not a troubleshooting step. Submitting apps that do not comply, expecting reviewers to find the problems, leads to rejections, review delays and lengthier appeal processes.

Google points to four common areas to double-check: app content and features, app targeting and content rating, functional reliability (no crashes, broken functionality or missing screens), and test credentials. If your app needs a login, provide valid, working credentials in Play Console so reviewers can test it fully.

Frequently asked questions