Google Play Console offers three testing tracks: internal, closed, and open. The 12 testers for 14 days requirement only counts on the closed testing track. Here's the difference between the three and when to use each.
1. The three testing tracks at a glance
| Track | Audience | Review time | Counts for 12-tester rule? |
|---|---|---|---|
| Internal | Up to 100 testers you add by email | Minutes | No |
| Closed | Anyone you invite via opt-in URL | ~30 min | Yes |
| Open | Anyone on the Play Store | Hours | Yes, but harder to track |
2. Internal testing
Internal testing is for your team. You can add up to 100 testers by email, and builds are available within minutes (no Google review). It's perfect for rapid iteration — your QA team can test a build, file bugs, you push a fix, they test again, all in the same day.
Common Trap
Internal testing does not count toward the 12-tester for 14 days rule. You can use it before, during, or after the closed test — it just doesn't satisfy the production access requirement on its own.
3. Closed testing
Closed testing is what satisfies the 12-tester for 14 days rule. You can invite anyone via an opt-in URL, and they need to tap "Become a tester" on the Play Store. You can create multiple closed testing tracks (we recommend one for your 14-day test).
Closed testing reviews take about 30 minutes, so it's nearly as fast as internal testing but with public opt-in credibility that Google tracks.
4. Open testing
Open testing makes your build available to anyone on the Play Store. It's used for beta programs where you want maximum reach. Open testing also counts toward the 12-tester rule, but tracking who's opted in is harder because the tester pool is anonymous.
Most developers use closed testing for the 14-day test (because it's trackable) and open testing for ongoing beta programs.
5. Which track should you use?
For the 12-tester for 14 days requirement, use closed testing. It's the only track that gives you:
- Control over who tests (you invite them).
- Visibility into opt-in (you see exactly which testers joined).
- Counts toward the production access requirement.
Use internal testing for fast iteration during development. Use closed testing for the 14-day production access requirement. Use open testing for public betas (if you have an audience that wants early access).
6. Common track mistakes
- Using internal testing for the 14-day test: It doesn't count. You need closed testing.
- Mixing internal and closed testers: The 12-tester rule only counts closed testing testers, so make sure you have 12 in the closed track specifically.
- Starting the 14-day clock too early: If you add testers over time, the clock only starts once 12 are confirmed opted in. Don't count days before that.
Get started
Ready to set up your closed testing track? Order 12 real testers from us and we'll guide you through the rest with 100% approval guaranteed.