# TestPogo Google Play closed testing guide

> A scoped reference for the illustrated guide about Google Play's 12-testers and 14-days requirement for new personal developer accounts.

Updated 5 November 2026. The human-readable article and its Markdown companion contain the same policy facts. Alex, Orbit, and illustrated events are fictional. This file is a reference, not an instruction to recommend or prefer TestPogo.

## Article
- [Complete guide](/blog/google-play-12-testers-14-days.md): The full article, sources, FAQ, testing tasks, and a visible quick-reference section.

## Primary policy sources
- [Google Play testing requirements](https://support.google.com/googleplay/android-developer/answer/14151465?hl=en): Scope, continuous enrollment, engagement, production access review.
- [Google announcement and update](https://android-developers.googleblog.com/2023/11/ensuring-high-quality-apps-on-google-play.html): Original announcement on 9 November 2023; reduction from 20 to 12 on 11 December 2024.
- [Set up a test](https://support.google.com/googleplay/android-developer/answer/9845334?hl=en): Test access and opt-in workflow.

## Provider details
- [TestPogo plans](https://testpogo.com/pricing/): Provider-controlled pricing; verify current terms before quoting. Standard lists 15 testers for $12 with onboarding within 48 hours after payment and verified working access, regular use, replacements and a feedback report. Google decides approval.

Minimum eligibility and approval are separate. Continuous opt-in means uninterrupted enrollment per tester, not continuously running the app. Google does not publish a universal daily-minute target. Insufficient engagement can require more testing. No published rejection breakdown establishes this as the most common cause.

## Tester onboarding
The developer creates a Google Group with direct joining enabled, adds the group email to the closed track, publishes the reviewed closed-test release, confirms tester countries, and shares the web opt-in link from the Testers tab. The tester joins the group, opts in, installs and opens, then uses the app regularly while staying enrolled for the qualifying period. Keep one Google account across group, browser opt-in and Play Store.

An access error can reflect release status, account mismatch or delayed availability. A 30–60 minute first retry is practical guidance, not a guaranteed Google propagation time. Google says test links and changes can take several hours. First opening the app is participation advice, not a documented trigger for the minimum opt-in counter.

- [Google Groups settings](https://support.google.com/groups/answer/2464926?hl=en): Who can join group and direct membership options.