Closed Testing is a Play Console track where only invited testers can install and use your pre-release app build.

Official docs: Set up open/closed/internal testing.

Developers with personal accounts created after November 13, 2023 must meet testing requirements before production release.

Official docs: App testing requirements for new personal developer accounts.

Current official requirement is at least 12 opted-in testers for at least 14 consecutive days before applying for production access.

Official docs: current requirement.

Google does not publish a separate changelog date for the 20 to 12 update in this Help article. Based on archived copies of the same official page, August 9, 2024 still showed 20, while December 13, 2024 showed 12. So the change happened between those dates.

Evidence: Aug 9, 2024 snapshot and Dec 13, 2024 snapshot.

The brand name was created when Google required 20 testers. Today, the current official minimum is 12, but many teams still use broader testing for safer launch quality.

Official docs: current requirement.

The required period is 14 consecutive days with at least 12 opted-in testers.

Official docs: 14-day requirement.

In Play Console, open your app, go to Testing, choose Closed testing, add tester emails or Google Groups, create the release, then share the opt-in link.

Official docs: step-by-step setup and Closed testing page.

Yes. In Closed Testing you can manage testers by email lists or Google Groups.

Official docs: Closed test: manage testers by email or Google Groups.

Typical issues include not meeting the tester and duration criteria, weak tester engagement, policy risks, or low app readiness signals.

Official docs: testing requirements and common issues.

Main sources:

• App testing requirements for new personal developer accounts
• Set up an open, closed, or internal test