BetaPod
← All posts

Closed Testing vs Internal Testing vs Open Testing on Google Play

· 4 min read

Google Play has three testing tracks. They look similar in the console but behave differently — and only one counts toward the 12-tester rule.

Internal testing

  • Up to 100 testers, added by email.
  • No review. Fast publish.
  • Good for: your dev team, build verification.
  • Does not count toward 12-tester rule.

Closed testing

  • Up to thousands of testers via Google Group, email list, or opt-in URL.
  • Subject to Google review (usually a few hours, sometimes days).
  • Good for: pre-launch tester cohorts, the 12-tester gate.
  • This is the one that counts.

Open testing

  • Anyone with the public testing URL can join.
  • Listed on Play Store under “Join the beta”.
  • Good for: scaling once you've already cleared the 12-tester gate.
  • Doesn't count toward 12-tester rule (open isn't closed).

If you're new and trying to ship, set up closed testing first. Internal and open are for after you're in production.

Closed Testing vs Internal Testing vs Open Testing on Google Play · BetaPod