How to Choose a Google Play Closed Testing Service
Choose a Google Play closed testing service by checking six things: how testers join your test, how many will be opted in compared with Google's minimum of 12, whether they engage for all 14 days, what feedback and report you get, what the refund terms exclude, and when you pay.
Google does not certify or recommend closed testing services, and nothing in its Help Center says you need one. If you decide to pay for testers, the useful questions are the ones that map to what Google actually checks. This checklist sets them out without naming any provider. The last section shows how we answer the same questions, so you can compare.
The Google facts here come from App testing requirements for new personal developer accounts and Set up an open, closed, or internal test.
How will the testers join your test?
In a closed test you manage testers by email list or Google Groups, testers need a Google Account or a Google Workspace account, and each tester opts in using your opt-in link. For a test that uses a Google Group, users must join the group before they can opt in. Google also says that a user who opts in to your internal test is not eligible for your closed test until they opt out of the internal one.
None of these steps requires anyone outside your team to sign in to your Play Console account. Ask a service to work with your opt-in link and a tester list or group, and be cautious of one that asks for your Play Console login. Our closed testing setup guide shows where the lists and the link live.
How many testers will be opted in?
Google's minimum is 12 testers opted in when you apply, each opted in continuously for the preceding 14 days. Testers who opt in and then opt out before 14 days do not count, and a tester who rejoins needs 14 consecutive days again. With exactly 12, one departure puts you below the line.
Ask how many testers will be opted in, not invited, and whether there is a buffer above 12. Ask what happens if a tester drops out part-way.
Will testers engage for all 14 days?
When you apply, Google asks about tester engagement during your closed test, including whether testers used all available features and whether their usage matched expected production behaviour. Insufficient tester engagement is one of the two reasons Google gives for required continued testing.
Ask how often testers open the app, whether that continues for all 14 days, and what they are asked to test. Google's own advice is to give testers clear instructions, say what feedback you want and encourage them to use as many features as possible.
What feedback and report will you get?
Google says you must summarize your testing feedback when applying for production access, describe how it was collected, and describe the changes you made based on the closed test. Feedback you can quote is therefore part of what you are paying for.
Ask what format the feedback takes, whether it includes screenshots, and whether you get a report at the end. Note that Google says testers cannot leave public reviews on Google Play for test versions, so reviews are not something a closed test can deliver.
What do the refund terms cover and exclude?
No service can honestly promise production access, because Google makes that decision. Fair refund terms are tied to what the service controls, such as the tester count, the 14 days and engagement, and they say plainly what is excluded, such as declines for reasons related to the app itself.
Ask whether the terms apply to every package, what proof you need to send, and whether you can choose between a refund and a new test.
When do you pay?
Google has no rules on this, so it is purely a question for the provider. Ask whether you pay everything up front or part at the start and part when the report is delivered, and what happens if the test stops early.
How TestersFourteen answers these
| Question | Our answer |
|---|---|
| How testers join | We send you a CSV of tester emails. You upload it to your closed testing email list in Play Console and send us your opt-in link, and our testers opt in with that link. |
| Start time | Testers usually start joining within 10 minutes after the CSV is uploaded and we have your opt-in link. |
| Testers vs 12 | Basic: 12 testers, Google's minimum, no extra buffer. Pro: 20+ testers, at least 8 above the minimum. Max: 30+ testers, at least 18 above the minimum. |
| Engagement | Testers open and use your app every day for 14 continuous days. |
| Feedback and report | Feedback with screenshots (detailed feedback on Pro and Max) and a day-14 report. |
| Refund terms | Pro and Max include the refund or re-test promise below. Basic does not include it. |
| Payment | 50% to start and 50% on day 14, when your report is delivered. |
| Who tests | Real people using their own Android devices and Google accounts. |
Applies to Pro and Max.
Refund or re-test promise: Google tells you why it declined production access. If the reason is on our side — fewer than 12 opted-in testers, fewer than 14 days, or insufficient tester engagement — you choose: a full refund or a new 14-day test at no extra cost. Just send us Google's decline message. If Google declines for a reason related to the app itself (for example policy, crashes, app quality or store listing), the promise does not apply.
Prices and the full comparison are on our pricing page, and the promise is set out in our refund policy. If you are still deciding whether to pay at all, our comparison of free vs paid testers covers what a free exchange does well.
Frequently asked questions
Do I need to give a testing service access to my Play Console?
Google's closed testing setup does not require it. You add testers by email list or Google Group, and each tester opts in with your opt-in link, so a service needs your link, not your Play Console login.
How many testers should a closed testing service provide?
At least 12 must be opted in continuously for the 14 days before you apply. A number above 12 gives you a margin if a tester leaves, because Google says testers who opt out before 14 days do not count.
Can a closed testing service promise production access?
No. Google makes the decision on production access. What a service can control is the testing itself: how many testers are opted in, for how long, and how they engage.
Can testers leave public reviews during a closed test?
No. Google says testers cannot leave public reviews on Google Play for test versions. They can send private feedback through Google Play or through the feedback channel you provide.