Internal vs closed vs open testing on Google Play
Three testing tracks, three different jobs. Only one of them satisfies the 12-testers-for-14-days requirement - here is which, and why the others do not count.
Internal testing
Up to 100 testers, available almost immediately after upload, with no review delay worth speaking of. This is the track for your own team - the build you push twenty times a day while you are still finding your feet.
Internal testing does not count toward the production access requirement. Not for any of the fourteen days. Developers regularly run a perfect internal test for a month and then discover it bought them nothing.
Closed testing
This is the one that counts. Closed testing uses either an email list or a Google Group, testers must opt in through a link you share, and it is the only track that satisfies the twelve-testers requirement.
The 14 days must be consecutive. If your tester count drops below twelve partway through, the streak is what suffers - so build in margin rather than running at exactly the minimum.
Open testing
Anyone with the link can join, and your app becomes discoverable on Play with a beta label. Useful for scale, but it is not a substitute for closed testing when you are working toward production access.
Open testing also exposes an unfinished build to the general public, which is a real reputational cost if your app is not ready for strangers.
The order that works
Run internal testing while the build is still moving. Move to closed testing once it is stable enough that twelve people can use it daily for two weeks without hitting a wall. Use open testing after production access, if you want a public beta channel at all.
- Internal: your team, instant, does not count
- Closed: 12+ opted-in testers, 14 consecutive days, this is the requirement
- Open: public beta, discoverable, not a substitute