Google Play has three testing tracks. Internal testing is for you and your team: up to 100 people, and builds reach them within minutes. Closed testing is an invite-only group, and it's the only track that counts toward the rule new personal accounts have to pass: 12 testers opted in for 14 days in a row. Open testing is a public beta that anyone can join from Google Play, and on a new personal account it stays locked until you have production access. So the usual order is internal while you build, closed to qualify, then production, plus open testing if you still want a public beta.
Short version: only closed testing counts for the 12 testers, 14 days rule. Internal testers don't count, and a new personal account can't use open testing until Google grants production access.
The three tracks side by side
The figures come from Google's Play Console Help articles on setting up a test (answer 9845334) and on testing requirements for new personal accounts (answer 14151465), read in October 2026.
| Internal | Closed | Open | |
|---|---|---|---|
| Who can join | People you add by email | People on your email lists or in your Google Group | Anyone who finds the test on Google Play |
| How many | Up to 100 per app | Email lists of up to 2,000 people each (50 per track), or Google Groups | Unlimited, or a cap you set of at least 1,000 |
| Review before testers get it | No standard review, usually live in minutes | Normal app review | Normal app review |
| Listed on Google Play | No | No | Yes |
| Counts for the 12-tester rule | No | Yes | No |
| On a new personal account | Available | Available, and required | Locked until production access |
| Paid apps | Testers install free | Testers pay | Testers pay |
| Tester feedback | Private to you | Private to you | Private to you |
| Best for | You and your team, quick checks | Real users, and passing the rule | A public beta |
Internal testing: your team, in minutes
Internal testing is the fast lane. You add up to 100 testers by email, upload a build, and it reaches them within minutes. Google says internal releases may skip the usual policy and security review, which is why they're quick. Internal testers install paid apps for free, and they get the app even in countries where it isn't available yet.
Use it for yourself, your co-founder and anyone who needs today's build. Don't use it for the 12 testers: internal opt-ins don't count toward the rule, no matter how long they stay.
Play Console also has internal app sharing, which sits outside all three tracks. You upload a build, get a link and send it to people you've allowed. There's no review and no version code to bump, and it doesn't count toward production either.
Closed testing: the track that counts
Closed testing is invite-only. Testers join through an email list you manage in Play Console or through a Google Group, opt in from the link you share, then install from Google Play. Every closed release goes through Google's review first. On a new account we usually see that take a day or two, sometimes longer.
For a personal developer account created after 13 November 2023, this track is the gate. You need at least 12 testers who have been opted in for the 14 days before you apply, and only then can you ask for production access. Organization accounts and older personal accounts are exempt, although a closed test is still the cheapest way to find out what strangers make of your app.
When does the 14-day clock start?
There isn't one clock for the whole test. Google looks back from the day you apply: on that day, at least 12 testers must each have been opted in for the previous 14 days without a break. Uploading the build doesn't start anything. If your 12th tester joins on day 3, your earliest application date moves back with them.
What happens if a tester drops out?
Their days stop counting. Google says testers who opt out before 14 days aren't counted, and someone who opts out and back in needs 14 new consecutive days. Everyone else's days keep counting, so nothing is lost as long as 12 testers still have their full 14 when you apply. You only lose time if you fall below 12 and have to bring someone new in, because the newcomer starts from zero. That's why closed testing services put more than 12 people on a track. TestFi puts 16.
Can I update the app during the 14 days?
Yes. A new build goes through review again, but it doesn't reset anyone's days, because Google counts opt-ins, not versions. Shipping a fix mid-test also gives you something real to write on the production form, which asks what you changed because of testing.
Do testers have to open the app every day?
Google doesn't publish a minimum such as a daily open. It does say it may ask for more testing if engagement was low, and the production form asks how testers used the app. Twelve installs that nobody touched after day one are the classic way to get a "more testing required" reply.
Open testing: a public beta, later
Open testing lists your test on Google Play and anyone can join. You can leave it unlimited or set a cap of at least 1,000 testers. It reaches more people before launch than you would ever recruit yourself, on phones and in countries you don't have.
There are two catches. On a new personal account, Play Console keeps open testing locked until production access is granted, so it can't replace the closed test and doesn't count toward it. And because anyone can join, you have much less say over who you hear from.
Open beta vs closed beta
In a closed beta you pick who's in, and the group is small enough to talk to each person. In an open beta people pick you, and most of them never write a word. Roughly, a closed beta tells you why something fails and an open one tells you how often.
Move from closed to open once people who've never seen the app can get through the core flow, and the reports coming back are about features rather than crashes.
When a tester is on more than one track
- Someone who qualifies for several tracks gets the build with the highest version code. Number internal builds above closed ones and your team always gets the newest.
- Someone opted in to internal testing has to opt out before they can receive closed or open builds. If you add yourself to both, leave internal first.
- Feedback from testers is private on every track. Nobody can leave a public review of a test build.
Release review vs production access review
These are two different reviews and they're easy to mix up. Release review happens every time you send a build to the closed or open track, and later to production. Google checks the build against its policies before testers can install it.
Production access review happens once. After the closed test qualifies, you answer a questionnaire in Play Console and apply, and Google decides whether the account can publish. Google says this review usually takes 7 days or less. Finishing the 14 days doesn't approve you on its own: if engagement looked thin, Google can ask for more testing, and you're back to recruiting. If that has already happened, what to do after a production access rejection walks through it.
What to record for the production access form
The questionnaire has three parts, and the first and last are about your test. They're much easier to answer if you collect the evidence while the test runs rather than trying to remember it afterwards.
| Part of the form | What it asks | What to keep |
|---|---|---|
| About your closed test | How you recruited testers, how they engaged, what feedback you got and how you collected it | Who joined and when, each tester's notes, any bug reports or messages |
| About your app | Who it's for, what it does for them, how many installs you expect | Your one-paragraph pitch, and what testers said the app was for |
| Production readiness | What you changed because of testing, and how you know it's ready | A list of fixes made during the test, each tied to the feedback behind it |
The strongest thing you can point to is a tester hitting a bug on video, followed by the build that fixed it. Neither the rule nor the form asks for recordings, but they turn "testers engaged" from a claim into something you can show.
On a TestFi closed test, every tester writes notes on day 7 and day 14, and the draft answers for the form are written from those notes. Five screen recordings can be added at checkout for $26.95.
How long it takes in practice
In 112 TestFi closed tests up to 1 October 2026, the median time from publishing the test to the 12th confirmed install was 2.6 days. Add the 14 days, a day or two of release review at the start, and up to a week of production review at the end. About 17 days until you can apply, and up to a week more for the answer, is a realistic plan. The full spread is on the closed testing data page.
What about iOS?
Apple has no version of this rule. TestFlight takes up to 100 internal testers from your App Store Connect team and up to 10,000 external testers by email or public link. The first build you send to external testers goes through Apple's beta review, and nothing has to run for 14 days before you ship.
Which track should you use?
- You're building and only your team needs the app: internal.
- New personal account, ready for real users: closed, with at least 12 testers for 14 days. It's the only route to production.
- Organization account, or a personal account from before November 2023: closed if you want focused feedback first, otherwise straight to production.
- Already live and you want a wide beta: open.
If finding the 12 is where you're stuck, 12 testers for your closed test is what TestFi sells: 16 testers on your track for $39.99, notes from each on day 7 and day 14, and a free re-run if fewer than 12 are still opted in on day 14. The free routes are in how to get 12 testers yourself, and the rule itself is in what the 12-tester rule says.
Frequently asked questions
Does internal testing count toward the 12 testers requirement?
No. Google's requirement names a closed test, and only testers opted in to a closed track count. Internal testers don't count, however many you add and however long they stay.
Can I run internal and closed testing at the same time?
Yes. Plenty of developers keep internal for their own builds and closed for testers. One person on both tracks gets whichever build has the highest version code, and has to opt out of internal to receive closed builds.
Can I skip closed testing and go straight to open testing?
Not on a personal account created after 13 November 2023. Open testing stays locked until production access, and production access needs the closed test. Older personal accounts and organization accounts can go straight to open testing or production.
Does updating my app reset the 14 days?
No. The 14 days belong to each tester's opt-in, not to a build. A tester who opts out and back in does start over.
How many testers should I put on a closed test?
Google's minimum is 12 opted in on the day you apply. Put more than that on the track, because anyone who leaves early stops counting and a replacement starts from zero.
Do open testers leave public reviews?
Feedback through any testing track is private and comes only to you. Once the app is live in production, anyone who installed it can review it like any other user.