Short answer: only closed testing counts. If your personal Play Console account was created after November 13, 2023, Google requires a closed test with at least 12 testers who have been opted in continuously for the preceding 14 days before you can apply for production access (Play Console Help: app testing requirements). Days spent on the internal testing track don't add to that. There is also a catch most launch checklists skip: a tester who is opted in to your internal test can't receive your closed test until they opt out of the internal one (Play Console Help: set up an open, closed, or internal test).
The three tracks side by side
All rows below come from the two Play Console Help pages linked above.
| Internal testing | Closed testing | Open testing | |
|---|---|---|---|
| Who can join | Up to 100 testers per app, added by email list | Email lists (up to 2,000 testers per list) or Google Groups | Anyone on Google Play |
| When you can start | Before app setup is complete | After app setup is complete | After you gain production access |
| Counts toward 12 testers / 14 days | No | Yes | No |
| Paid apps | Testers install free | Testers must buy the app | Testers must buy the app |
| Speed | New bundles usually reach testers within minutes | The first test link can take several hours to go live | The first test link can take several hours to go live |
Internal testing is still worth using. It's the quickest way to catch a crash on launch before you invite anyone into the track that matters.
The overlap rule that quietly removes testers
Play Console Help states it directly: "A user who opts into your app's internal test is no longer eligible to receive an open or closed test. To access an open or closed test, the user must first opt out of the internal test and then opt in to the open or closed test." The same page adds that users opted in to internal testing "receive only the version code published on the Internal testing track", even if they are also listed as testers on other tracks.
In practice, if you reuse the same friends or teammates for both tracks, having their email on the closed track's list doesn't make them closed testers. Until they leave the internal test and join the closed one, they aren't receiving your closed test, and the requirement only counts testers who are opted in to the closed test.
Moving from internal to closed: the steps
- Smoke-test on internal. Go to Test and release > Testing > Internal testing, add a small email list, upload your bundle and confirm the app installs and opens.
- Pick your closed testers. Decide who will cover the 14 days. Keep this group separate from the internal list where you can.
- Move anyone who is on both. Ask them to open the internal test's opt-in link and opt out first. Only then should they open the closed test link and opt in.
- Set up the closed track. Go to Test and release > Testing > Closed testing > Manage track, open the Testers tab, choose email lists or a Google Group, add a feedback URL or email address, copy the shareable link and save.
- Allow for the first-link delay. Help says the first closed release link can take several hours to become available, so send invites once the link works, not the minute you publish.
- Start your own count. Write down the date each tester opts in to the closed test. The 14 days only work for you once at least 12 of them are opted in and stay in. Help's FAQ is explicit: testers who opt out before 14 days don't count, and someone who opts out and back in needs 14 consecutive days.
Edge cases
- Shipping a fix mid-test. Upload the fixed build to the closed track. Avoid adding closed testers to an internal list to give them a hotfix faster: Help says internal opt-ins stop receiving closed builds, and it doesn't say how that affects their closed opt-in history.
- Paid apps. Closed testers have to buy a paid app, so plan for that or test with a free build.
- Countries. Help says internal testers get the build even in countries where your closed or open version isn't available. That exception doesn't extend to closed testers, so check the closed track's countries match where your testers are before you send invites.
- Reviews. Help notes that internal tests might not go through standard Play policy or security reviews. A build that works on internal can still hit a review on its first closed release, so leave room for that before day 1.
Checklist before you start counting
- [ ] Account type and creation date confirmed (personal, after November 13, 2023)
- [ ] Closed track release published and the opt-in link opens for a tester
- [ ] No closed tester is still opted in to the internal test
- [ ] At least 12 testers opted in to the closed test, each with a dated record
- [ ] Feedback channel set on the closed track's opt-in page
- [ ] Countries on the closed track match where your testers are
If recruiting and tracking a dozen testers isn't something you want to run yourself, TestMyApps provides managed closed tests with 14 testers over 16 days, from $15 one-time. Our comparison of Google Play internal testing and closed testing goes deeper on when to switch tracks.
Arun, founder of TestMyApps

