Question 1

What exactly does GetClosedTesting do?

Accepted Answer

We give you a place to run a Google Play closed testing campaign: a tester roster, a tracked campaign with dates and a current state, a progress dashboard, participation monitoring and a record of the feedback collected. The test itself still runs inside your Google Play Console account.

Question 2

Do you need access to my Play Console account?

Accepted Answer

No. You keep control of the Play Console. You tell us what you need tracked, we structure the campaign, and your team runs the track, the releases and the production access application.

Question 3

How soon can a campaign start?

Accepted Answer

Once the app is ready for the closed track and the tester roster is confirmed. Most of the setup work is gathering tester Google account addresses and agreeing the testing window, so the ramp-up depends on how quickly your list comes together.

Question 4

Which apps is this suitable for?

Accepted Answer

Any Android app distributed through Google Play that needs a closed testing track, including new apps from personal developer accounts submitting a production access application for the first time.

Question 5

What is a Google Play closed testing track?

Accepted Answer

It is a testing track in the Play Console that is limited to the testers you invite. You distribute a build to those testers, they install it from a Play opt-in link, and you collect feedback before release. Unlike open testing, nobody outside the invited list can join.

Question 6

What is the 12 tester requirement?

Accepted Answer

Google asks developers on personal accounts to run a closed test with a minimum number of testers who stay opted in for a continuous period before production access is granted. The widely cited figure is 12 testers for 14 continuous days. Google controls this policy and has changed it before, so confirm the current number and duration in the official Play Console documentation before you plan around it.

Question 7

Does the requirement apply to organisation accounts?

Accepted Answer

The closed testing prerequisite has applied to personal developer accounts created after the policy change, with organisation accounts treated differently. Eligibility rules are set by Google and do change, so check the current requirements against your own account type in the Play Console.

Question 8

Can I reuse the same testers for the next release?

Accepted Answer

Yes. Testers stay opted in to your closed track once they accept, so a tester pool can serve several campaigns. Google's continuous-day requirement is why continuity matters: if testers leave and re-join, the clock can reset.

Question 9

Where do testers come from?

Accepted Answer

Most teams combine three sources: people already close to the product (colleagues, clients, communities), paid tester pools, and developer communities where testers trade opted-in installs. Which mix works depends on your budget, your timeline and how much real feedback you want.

Question 10

How do I know a tester is actually participating?

Accepted Answer

Opt-in and activity are two different things. A tester can accept the invite, install once and never open the app again. Track opt-in status separately from activity, and check both before you rely on the count.

Question 11

What happens if testers drop out mid-campaign?

Accepted Answer

You can invite replacements, but be aware that a gap in the tester count can affect a continuous-days requirement. Monitor participation continuously rather than checking once at the end, which is the main reason we built participation tracking into the campaign view.

Question 12

Do testers need a Google account?

Accepted Answer

Yes. Testers opt in with the Google account signed in to the Play Store on their device, and each address can only fill one slot, so collect accurate addresses rather than duplicates.

Question 13

How is pricing structured?

Accepted Answer

Plans are defined by how many campaigns you run at once, whether tester pools are reusable and how much hands-on support you need. Current rates are confirmed in writing before a campaign starts so there are no surprises.

Question 14

What is not included in the price?

Accepted Answer

Google Play fees, any cost of paid tester recruitment, and the development work required to fix issues found during testing.

Question 15

Do you charge per tester?

Accepted Answer

Pricing is campaign based rather than metered per tester. Tester scope is agreed at kickoff so that the roster size matches the requirement you are working against.

Question 16

When am I billed?

Accepted Answer

Before the campaign starts. You receive an itemised summary of what is covered and the agreed testing window.

Question 17

Does using GetClosedTesting guarantee production access?

Accepted Answer

No, and you should be cautious of anyone who says otherwise. Production access is granted by Google after it reviews your account and your testing evidence. Our job is to make your testing organised and your evidence easy to present, not to influence Google's decision.

Question 18

What does Google look at?

Accepted Answer

Google reviews whether the app is ready for release, whether the testing requirement has been met, and whether the information you provide about the app and its testing is accurate and consistent.

Question 19

How do you help with the application?

Accepted Answer

We keep a clean record of your testing window, your tester participation and the feedback you received, which makes it much easier to answer the questions in the production access form accurately. On the Scale plan we review that evidence with you before you submit.

Question 20

What if the application is rejected?

Accepted Answer

You can fix the underlying issue and apply again. Where the reason relates to testing, we help you work out whether the problem was the testing window, tester participation, app readiness or the accuracy of the form itself.

Question 21

Which Android versions do you support?

Accepted Answer

Your build's own minimum and target SDK levels decide what can be tested. We track the device and OS version of each tester so you can see how wide the coverage actually is rather than assuming it.

Question 22

How is feedback captured?

Accepted Answer

Feedback is recorded against the campaign and the build under test, with the tester, device details, steps to reproduce and severity where they are known.

Question 23

Can I import an existing tester list?

Accepted Answer

Yes. Existing spreadsheets are usually the fastest way to seed a roster, and the roster then becomes the system of record instead of drifting from it.

Question 24

Is there an API?

Accepted Answer

Not today. If your team needs programmatic access, tell us during onboarding: it is the most common request we see from teams running several apps.

Question 25

What is the refund policy?

Accepted Answer

The Refund Policy page sets out when a refund is available. The short version: if we have not started campaign work, you are not out of pocket; once work has begun, refunds are considered against the work completed.

Question 26

How do I get support?

Accepted Answer

Email the support address in the footer. Starter and Growth plans are answered by email, Scale includes a named point of contact.

Question 27

Do you help fix the bugs testers find?

Accepted Answer

No. We organise the testing and the feedback. Fixing the app is your team's work, and keeping that boundary clear is what makes the testing evidence trustworthy.

Frequently Asked Questions

Getting Started

Google Play Testing

Testers and Participation

Pricing and Payments

Production Access

Technical Issues

Refunds and Support

Still Have a Question?