Internal, closed and open testing: which one Google counts
Play Console gives you three testing tracks and only one satisfies the 12 testers requirement. Here is what each track does and when to use it.
Published , 5 min read
Play Console offers three pre-production tracks. They look similar in the interface and behave very differently. Only one of them counts toward production access.
Internal testing
Up to 100 testers, no Google review of the build, available within minutes of upload. It exists for your own team to smoke-test a build before anyone outside sees it.
Counts toward the 12 testers requirement: no.
Closed testing
An invite-only track using an email list or a Google Group. Builds are reviewed by Google before testers can install. This is the track the requirement is written against.
Counts toward the 12 testers requirement: yes. This is the only one that does.
Open testing
Anyone can join from your Play Store listing without an invitation. Useful for a public beta once you already have production access.
Counts toward the 12 testers requirement: no, and you generally cannot run one before production access anyway.
Choosing correctly
If your goal is production access, use closed testing. Use internal testing alongside it if you want a fast lane for your own builds. Running both is fine and does not interfere with the count. Leave open testing for after you are live.
A note on the tester count
Testers on your internal track do not add to your closed track count, even if they are the same people. The two lists are independent. If you want someone counted, they must be on the closed track's tester list and must have opted in through the closed track's link.