Only the closed track counts toward Google’s 12-tester, 14-day requirement. Internal testing does not count, no matter how long it runs.
The three tracks compared
Who needs a closed test
Applies to you
A personal Play Console developer account created on or after November 13, 2023.
Doesn’t apply
Organization accounts, or personal accounts created before November 13, 2023.
Invite a few more than 12 testers to your closed test. If one person opts out mid-way, you don’t drop below the 12 you need to keep the window valid.
Quick answers
Can I run an internal test first, then switch to closed?
Yes, internal and closed tests are independent tracks. Running an internal test first is fine for catching early bugs. When you’re ready to start the 14-day clock, create a separate closed test. The days you ran the internal test do not count toward the 14 days.
Can I run closed and open tests at the same time?
Yes, the tracks are independent. Running an open test alongside your closed test is allowed. Only the opted-in closed testers count toward the 14-day requirement; open testers do not.
What if a tester opts out before day 14?
That tester stops counting. If they opt back in, their 14-day window restarts from zero. This is why inviting a small buffer above 12 is practical: one opt-out doesn’t drop you below the minimum.
What App Testers handles for you
- Real closed-track testers, opted in within 4 hours
- Kept active for all 14 days, replaced if one leaves
- Feedback and bug reports as you go
- Free re-test if Google asks for more testing
- Full refund if you cancel before testers join
Source: Google Play Console Help, “App testing requirements for new personal developer accounts”. Google can change these rules, so check its page before you start.