If your personal Play developer account was created after 13 November 2023, only one of the three testing tracks gets you to production: closed testing. Internal testing doesn't count toward the 12 testers for 14 days, and open testing stays locked until you already have production access.
That's the short answer. The rest is the four mistakes I see most from developers who run closed tests through TestFi. It's my product, so weigh that, but each of these mistakes costs about a week whoever you test with.
The three tracks side by side
| Internal | Closed | Open | |
|---|---|---|---|
| Who can join | People you add by email | Your email lists or a Google Group | Anyone who finds it on Google Play |
| How many | Up to 100 per app | Lists of up to 2,000 each, or Google Groups | Unlimited, or a cap of at least 1,000 |
| Review first | Usually live in minutes | Normal app review | Normal app review |
| Counts for the 12-tester rule | No | Yes | No |
| On a new personal account | Available | Available, and required | Locked until production access |
Mistake 1: running the 14 days on internal testing
Internal is the easy track. No review, and builds reach your phone in minutes. So people invite twelve friends there, wait two weeks, and then can't find an Apply for production button anywhere. Google only counts testers opted in to a closed track. Keep internal for yourself and your team, and put testers on closed.
Mistake 2: being on both tracks yourself
Someone who qualifies for more than one track gets the build with the highest version code. And anyone opted in to internal has to opt out before they can receive closed builds. If your own phone never shows the closed build, that's usually why: leave internal first. If your team should always get the newest build, number internal builds above closed ones.
Mistake 3: treating open testing as a shortcut
On a personal account created after 13 November 2023, open testing is locked until you have production access, and production access needs the closed test. You can't skip ahead. The order is internal while you build, closed to qualify, then production, and open testing after that if you still want a public beta. Older personal accounts and organization accounts can go straight to open.
Mistake 4: thinking day 14 is the finish line
There are two different reviews. Every build you push to a track goes through app review. Production access review happens once, after the closed test qualifies: you fill in a questionnaire in Play Console and Google decides whether the account can publish. Google says that usually takes 7 days or less.
Finishing the 14 days doesn't approve you on its own. The form asks what your testers did and what you changed because of them. I went through it question by question earlier in this series.
Updating the app during the test is fine, by the way. A new build goes through review again, but nobody's days reset, because Google counts opt-ins, not versions. A mid-test fix also gives you something real to write on that form.
How long the whole thing takes
Across 112 closed tests we ran up to October 2026, the median time to the 12th installed tester was 63.6 hours. Add the 14 days, a day or two of review at the start, and up to a week of production review at the end. Plan on about 17 days before you can apply.
The days count per tester. If your 12th person joins on day 3, your earliest application date moves back with them, and anyone who opts out and back in needs a new 14 days in a row. That's why paid services put more than 12 people on the track. TestFi puts 16 on yours for $39.99, with notes from each tester on day 7 and day 14.
The longer version, with paid apps, Google Groups and an FAQ, is in our internal vs closed vs open testing guide.
Top comments (0)