What is Closed Test Pro?

Closed Test Pro is an Android app that solves one problem: Google Play requires 12 testers to stay opted in for 14 consecutive days before a personal developer account can publish to production, and most developers cannot find 12 people who will stick around that long.

It works as a reciprocal community. You test other developers' apps to earn credits, spend those credits to list your own app, and the same community tests yours. Everyone in the pool is a developer who needs the same thing, which is why retention is far better than asking friends and family.

How the credit system works

Credits are earned by testing, and spent on listing your own app.

You earn credits the first time you complete a test on another developer's app: install it from their Play listing, use it, then tap Done. That first completed test is typically worth 5 credits. Some apps on paid plans are worth up to 10.

Daily verifications after that first test earn nothing. They are what keeps the community's apps alive, not a second income stream. This trips people up, so it's worth being blunt about: credits come from breadth (testing many apps), not from repetition.

What a listing costs

Twelve testers is the Google minimum, so 60 credits is the entry point. Most developers should aim higher. A 12-tester listing has no buffer, and a single drop-off puts you back under the line.

When the paid plan slots are already occupied, free listings carry a small credit surcharge. The app shows the exact cost before you confirm.

What you actually do each day

Daily Testing is the part that decides whether your 14 days count for anything. It is deliberately short.

For each app on your list:

1. Tap Open to launch the app directly
2. Use it for the required time: 30 seconds on days 1 and 2, 20 seconds from day 3 onward
3. Come back and tap Done

On days 2, 5, and 10 there's an extra step: you open the app's Play Store listing before Done unlocks. That's the mechanism for generating real Play Store feedback during the window, which is exactly what Google looks for when it assesses whether testing was genuine.

Reminders fire at 9am and 6pm local time so the streak doesn't die from forgetfulness.

Task Hub and Sparks

Task Hub is the newer half of the platform, and it exists because Daily Testing proves engagement but doesn't capture feedback.

An app owner posts a task to the testers already on their app. There are three types:

• App Update: ask testers to pull your latest build after you ship a fix
• Play Store Feedback: collect structured written feedback, with an optional screenshot
• Custom: anything specific you need checked

Testers submit, you accept or reject. Accepted submissions are the raw material for your production access application, where Google asks what feedback you received and what you changed because of it.

Sparks are not credits

Two separate currencies, and mixing them up is the most common confusion:

Rejected submissions cost the tester 3 Sparks, which keeps low-effort spam out of the system. Slots you post but nobody fills are refunded when the task is cancelled or the cycle ends. Sparks cannot buy listings and credits cannot buy tasks.

Plans

Every plan gets the same tracking, the same reminders, and real testers on real devices. Emulators are blocked across the board. Engagement Google can detect as fake is worse than no engagement at all.

The honest version: Free costs you time instead of money. Testing 12 apps at roughly a minute each per day is real effort. Pro and Premium skip the credit-earning entirely and give you a bigger tester buffer, which matters more than most people expect. With 20 or 30 testers, a few drop-offs never take you below 12.

Private Testing

There's a fourth option for apps you don't want listed publicly. Private Testing gives you 12 dedicated testers, keeps your app off the community Home feed entirely, and does not require you to test other developers' apps in return. It's the right choice for an unreleased product you'd rather not show to a few hundred other developers before launch.

Setting it up in Play Console

Closed Test Pro reaches your testers through a single Google Group. You add it once:

1. Open Play Console and go to Test and release, Testing, Closed testing
2. Choose Manage track, then the Testers tab
3. Under Google Groups, add closedtestproapp@googlegroups.com
4. Save, then send the change for review

That last step is the one people miss. Attaching a new group to a track is a configuration change that Google reviews. It will sit pending forever if you never submit it, and every tester will hit an "Item not found" error. Full troubleshooting guide here.

Because every tester joins the group before they ever see your app, you never have to collect and paste 12 individual email addresses.

When a tester cannot get in

Access problems are the most expensive failure in closed testing, not because they're hard to fix but because you normally don't find out until day 12.

When a tester cannot open your app, they report it from inside Closed Test Pro. You get an automated message naming the likely cause and listing the Play Console steps to fix it. After three reports of the same access problem, your listing is temporarily pulled from the pool so other developers aren't wasting daily tests on a link that doesn't work. Reply "Fixed" once you've sorted it and it goes straight back in.

Is reciprocal testing allowed by Google?

Worth addressing directly, because it's the first thing careful developers ask.

Google's concern is fabricated engagement: bots, emulators, accounts that install and never open the app, activity designed to look like testing without being testing. That is a policy violation and it can cost you your developer account, not just a rejection.

A reciprocal community is a different thing: real people, real devices, genuinely opening and using your app, leaving real feedback. Closed Test Pro blocks emulators and verifies actual app opens rather than installs for exactly this reason.

What it cannot do is make a weak app pass. Google reviews your production access application as well as your numbers, and testers who install but never engage will hurt you regardless of where they came from.

Frequently asked questions