Internal vs. closed vs. open testing on Google Play: only one counts toward the requirement

Three tracks, only one counts

Play Console has three testing tracks you can use before releasing to production: internal testing, closed testing, and open testing. The names are easy to mix up, but for the release requirement on personal developer accounts, 12 testers for 14 days only counts in closed testing. Even if you put 12 people in internal testing and wait 14 days, you can’t apply for production access.

At a glance

The table is based on Play Console Help: Set up an open, closed, or internal test and App testing requirements for new personal developer accounts.

Internal testing — checking it yourself first

This is the track for quickly getting a build in front of a small group of people you trust. You can add up to 100 testers per app, and you can start even if you haven’t finished setting up your app. Use it to check, on your own devices and your teammates’, that a build installs and the first screen loads.

• Internal testers install even paid apps for free.
• Testers in countries where you don't distribute your app can still join an internal test.
• It doesn’t count toward the requirement. However many people stay in it for however many days, it has nothing to do with applying for production access.

Closed testing — meeting the requirement

Only people you choose can join this track. You pick testers with email lists or Google Groups and send them an opt-in link. You can only use it once your app setup is complete, and testers can only install the app if their countries are included in the track’s countries / regions.

Personal accounts created after November 13, 2023 can only apply for production access once at least 12 testers have been opted in for 14 days in a row on this track. The steps for creating the track and adding testers are in the Play Console setup steps in our closed testing requirements guide, with screenshots.

Open testing — a wide trial right before launch

Anyone can find and join this track on the Play Store. Your store listing becomes public, so use it once your app and listing are ready to show to others. Accounts subject to the requirement can only use this track after getting production access, so there’s no way to gather 12 testers through open testing.

Common mistakes

• Spending the 14 days in internal testing. This is the most common one. If the requirement progress on your dashboard is stuck at 0, start by checking which track your testers are actually on.
• Counting internal testers as closed testers. According to Google’s documentation, users who have joined an internal test can’t join a closed or open test for the same app. They have to leave the internal test first.
• Creating a new closed testing track partway through. If you switch tracks, the opt-in time built up so far doesn’t carry over.
• Only adding testers to the list. Uploading emails alone doesn’t count them. Testers have to opt in through the opt-in link.

The order to use them in

1. Use internal testing (optional) to check installs and first launch on your own device.
2. Get at least 12 testers into closed testing and keep them there for 14 days. Ship a few new versions along the way.
3. Apply for production access from your dashboard and answer the questionnaire.
4. Once approved, use open testing for a wider trial if you need it, then release to production.