How Closed Test Pro closed testing works
The real product flow covers credits, Google Group access, Play listing links, Daily Testing, and tracking. It is not a DIY email-list walkthrough.
What Google Play requires
For personal developer accounts created after November 13, 2023, Google requires at least 12 opted-in testers for 14 consecutive continuous days before you can apply for production. Organization accounts that complete D-U-N-S verification are exempt from this closed-testing gate.
Opt-in alone is not the whole story. Testers still need to install and use the app. Closed Test Pro is built around that engagement window: community matching, Daily Testing confirmation, reminders, and activity visibility.
12+ Testers
At least 12 unique testers must opt in on personal accounts created after Nov 13, 2023
14 Consecutive Days
The testing window must stay continuous, since a quiet day can reset progress
Real Engagement
Opt-in alone is not enough; testers need to install and actually use the app
Production Application
After a solid 14-day run, apply for production access in Play Console
How it works in Closed Test Pro
Follow the same sequence the app uses, not a hand-built tester email list.
Download Closed Test Pro and join the Google Group
Install Closed Test Pro from Google Play, create your account, and join the community Google Group. Testers use that same group membership so they can open closed-testing listing links.
- Download Closed Test Pro from Google Play
- Join the Closed Test Pro Google Group (shown in the app onboarding)
- Use a real Android device, because emulators are blocked for earning credits
Earn credits (Free) or use a paid upload credit
On Free, you earn credits the first time you successfully install and confirm another developer’s app in Closed Test Pro (typically +5 credits). You need 60 credits for a standard free upload. Pro and Premium skip credit farming. You use a purchased upload credit instead.
- Open apps from Home, install from the Play listing link, then tap Done to earn credits
- Credits are granted once per app on first completed test, not for every daily open
- Free tiers: 60 credits for 12 testers, 75 for 15, 100 for 20, 150 for 30
- Pro ($9.99 / 20 testers) and Premium ($21.99 / 30 testers) upload without community credits
Set up Closed Testing in Play Console (still required)
Closed Test Pro does not replace Play Console. You still create a closed testing track and upload your AAB/APK there. Then add the Closed Test Pro Google Group under Testers → Google Groups, not a hand-built list of 12 personal emails.
- In Play Console go to Testing → Closed testing and create/manage your track
- Upload your app bundle (or APK) and publish the closed release
- On the Testers tab, add closedtestproapp@googlegroups.com under Google Groups
- Save and submit for review so the opt-in / listing link works for the community
Submit your Play listing link in Closed Test Pro
Inside the app, upload your listing: name, description, icon, and your Google Play store / closed-testing link. You do not upload an APK to Closed Test Pro. Free listings appear on Home for the community; Pro/Premium get priority placement.
- Paste the Play Store details link (package id in the URL)
- Confirm the Google Group was added so testers are not blocked (“Item not found”)
- Free uploads spend credits; Pro/Premium consume one plan upload credit
- Free owners also start a mutual Daily Testing cycle for 14 days
Community testers install and confirm in the app
Testers discover your app inside Closed Test Pro, open your Play link, opt in / install, then confirm in Closed Test Pro. They are not invited by a custom email blast from you.
- Testers find your listing in Closed Test Pro and open the Play link
- They install from Play Store and return to Closed Test Pro to tap Done
- Your tester count and activity update in the app’s tracking views
- Your app’s 14-day cohort clock starts once enough testers have joined (baseline 12 for standard free)
Hold the 14-day Daily Testing streak
Testers open each assigned app daily and confirm in Daily Testing. Reminders help keep the streak intact. Free owners must keep up their own daily testing so their listing stays healthy; Pro/Premium owners are not required to do mutual daily verification.
- Each app needs 30 seconds of use on days 1 and 2, then 20 seconds from day 3 onward, before Done unlocks
- On days 2, 5 and 10, testers open your Play Store listing before they can mark the day complete
- Reminders fire at 9am and 6pm local time so the 14-day window does not stall
- Tester Protection can raise capacity so drop-offs can be replaced during the eligible window
- After a solid 14-day run, apply for production access in Google Play Console
New: Task Hub
Task Hub sits alongside Daily Testing. App creators can post short, focused tasks for the testers already on their app. Examples include asking for private feedback, trying a specific screen, or capturing a screenshot. Testers complete tasks optionally and earn Sparks when a submission is accepted.
- Posting costs 2 Sparks per tester slot; unused slots are refunded when you cancel or when the cycle ends
- Accepted submissions earn the tester +2 Sparks; rejected ones cost −3 Sparks (anti-spam)
- You only see tasks for apps you are actively testing
- Completing tasks is optional, but Daily Testing is still what keeps the 14-day streak healthy
- Sparks are separate from credits: Sparks power Task Hub; credits unlock free uploads
Important distinctions
Play Console vs Closed Test Pro
You still publish the closed release in Play Console. Closed Test Pro takes your Play listing link, matches community testers, and tracks Daily Testing. It does not host your APK.
Google Group, not a private email roster
Add closedtestproapp@googlegroups.com under Google Groups on your closed track. You do not need to collect and paste 12 personal emails for Closed Test Pro to work.
Credits vs Sparks (Task Hub)
Credits unlock free app uploads. Sparks are Task Hub currency: post tasks (2 Sparks per slot) or earn Sparks by completing accepted tasks. Sparks cannot buy uploads.
Free vs Pro / Premium
Free relies on earned credits and mutual Daily Testing. Pro and Premium use a paid upload credit, get more testers and priority, and do not require owners to run the mutual daily-testing cycle.
Do not run an internal test alongside this
Google blocks anyone opted into your internal test from joining an open or closed test, even if they are on the closed track list. Country targeting and device exclusion rules are also ignored on internal but enforced on closed, so a tester who worked on internal can fail on closed for three separate reasons.
The challenge most developers face
Finding and managing 12 reliable testers who will consistently use your app for 14 consecutive days is one of the biggest challenges for indie developers. Common problems include:
- Testers forget to open the app daily
- No way to see whether testers are actually testing
- Testers uninstall midway and break the consecutive window
- Friends and family are unreliable for a full 14 days
- Difficulty finding strangers who will stay engaged
- No daily confirmation or reminder system
Closed Test Pro is built for that 14-day window
Community matching, Daily Testing, Task Hub, reminders, and activity tracking. Free via credits, or Pro / Premium for priority and more testers.
