All posts

Google Play internal, closed or open testing: which track

· 5 min read

Play Console gives you three testing tracks: internal, closed and open. They look alike. A common mistake is to run an internal test for two weeks and then find out it doesn't count for the 12-testers rule. This post explains what each track is for, which one counts, and what order I'd use on a new personal account.

What Google says each track is for

I read Google's page Set up an open, closed, or internal test on 10 November 2026. Here is the short version.

Internal testing. For quick checks with a small group.

  • Up to 100 testers per app, added by email list.
  • New builds reach testers within minutes.
  • Testers can't find the app by searching Google Play. You share a link.
  • Google says internal tests "might not be subject to standard Play policy or security reviews."

Closed testing. For pre-release versions with a wider group you pick.

  • Testers come from email lists or Google Groups. Only the people you add can join.
  • Email lists have limits: 2,000 testers per list, 50 lists per track, 200 lists per developer account. Google Groups have no size limit.
  • Testers can't find the app by searching. They use an opt-in link.

Open testing. For a large group, with the test visible on Google Play.

  • Anyone with the link can join. For a new app that isn't in production yet, people can also find the test in Play search.
  • The number of testers is unlimited by default. If you set a limit, it must be at least 1,000.
  • Google says to make sure your app and store listing are ready for visibility on Google Play before you choose this.

Is a test release reviewed?

The only thing Google's page says about review is the internal-testing line above: it might not go through the standard policy or security review. It says nothing about review for closed or open tests, so I won't guess. After the first publication of any test type, Google says the test link can take several hours to become available.

Which track counts for the 12 testers rule

Google's app testing requirements page says personal accounts created after 13 November 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. It says you must run a closed test before you apply for production.

Internal testing is described there as optional but recommended as a starting point. The page doesn't say internal testing counts toward the 12. And it says open testing becomes available after you gain production access.

So for a new personal account, the practical result is this. Internal testing is fine for your own fast checks. It does not satisfy the requirement. Open testing is not available yet. The closed test is the one that counts. The 12 testers for 14 days post covers the rule in full.

How testers join

  • Internal: you add emails to a list, then share the link.
  • Closed: an email list or a Google Group, plus the opt-in link. With a group, people must join the group before they opt in. Steps are in how to add testers to a closed test.
  • Open: a shared link, Play search for a new app, or the store listing once there is a production version.

On all tracks, testers can't leave public reviews for test versions. Google says their feedback won't affect your public rating. In open and closed tests they can send private feedback through Google Play. Google also tells you to give a direct channel, such as an email address or a website.

Quick comparison

  • Internal: up to 100 testers, email list, hidden from search, does not count for the 12.
  • Closed: email lists or Google Groups, hidden from search, opt-in link, this is the one that counts.
  • Open: anyone with the link, visible on Play, unlimited by default, available after production access per Google's requirements page.

A sensible order for a new personal account

Google doesn't prescribe this order. It's my advice, built on the facts above.

  1. Internal test first. Upload a build, add yourself and a friend or two, and check that it installs and the main flow works. Builds arrive in minutes, so this is quick.
  2. Closed test next. Add more than 12 testers and ask them to stay opted in. Keep it running for at least 14 days in a row. Give them a task and a feedback channel. How to write a test task helps here.
  3. Apply for production. Do it on or after day 14. See the production access post for what Google asks.
  4. Open testing, only if you want it. It's optional. Use it later for a wider public beta, once your store listing is ready for people to see.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps: you test someone's app, they test yours. Sign-in is with X, and new accounts start with 3 credits.

It fits the closed-test step. A reviewer can join your closed test if your test task includes the opt-in link and asks them to. A TestSwap review is a text form on our site. It is not a Play opt-in. Only people who opt in to your test through Google count toward the 12. TestSwap can't guarantee a number of testers or make anyone stay opted in, and it has no say in Google's decision.

Try it

When your closed test is live, post your app on TestSwap with a task that says exactly what to do. Reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).