How to Find 12 Android Testers for Google Play Closed Testing

Google Play closed testing can be one of the most frustrating parts of launching your first Android app.

For certain personal developer accounts, building the app is no longer the final step before production. You also need to run a closed test with enough testers for long enough before you can apply for production access.

If you are trying to understand the requirement, find 12 testers, or make sure your testing period is actually useful, this guide walks through the process from start to finish.

The short version

If you have a personal Google Play developer account created after November 13, 2023, Google currently requires you to run a closed test before applying for production access.

At the time you apply:

• At least 12 testers must be opted into your closed test.
• Those testers must have remained opted in for at least 14 consecutive days.
• You will then need to answer questions in Play Console about your test, your app, and its readiness for production.

Meeting the 12-tester and 14-day threshold allows you to apply for production access. It does not guarantee approval. (Google Support)

Who does the 12-tester requirement apply to?

The requirement specifically applies to personal developer accounts created after November 13, 2023.

If your account falls into this category, closed testing becomes part of the path to production.

The most reliable source for your exact situation is always your own Play Console, because Google may update its policies or apply requirements based on your account and app.

What does “12 testers for 14 days” actually mean?

The important word is continuous.

A tester who joins for a few days, leaves the test, and later joins again does not simply combine those periods into one continuous 14-day period.

That is why getting exactly 12 people is risky.

If one person opts out during the testing period, you may no longer have the minimum number of continuously enrolled testers required when you apply.

A practical approach is to recruit a few more than the minimum whenever possible.

What should your testers actually do?

The formal eligibility requirement focuses on testers remaining opted into the closed test for the required period.

But the purpose of closed testing is not simply to collect 12 email addresses.

Your testers should ideally:

1. Join the testing group or tester list.
2. Opt into the closed test.
3. Install the app from Google Play.
4. Open and use the app.
5. Try important features.
6. Report bugs, confusing flows, or usability problems.
7. Stay opted into the test for the full required period.

Google also recommends collecting and keeping track of tester feedback because you may be asked about what you learned and what you changed when applying for production access. (Google Support)

You do not need to invent artificial daily activity just to create numbers. Focus on real testing and useful feedback.

How to set up your closed test

A typical workflow looks like this:

1. Prepare your app in Play Console

Complete the required app setup and upload the build you want to test.

Before recruiting people, make sure your test build is stable enough for someone else to install and understand.

2. Create a closed testing track

Create your closed test in Play Console and configure who can participate.

Depending on your setup, you may use an email list or Google Group to manage access.

3. Share the correct access flow

Your testers may need more than one link.

Make sure they understand the order:

*Join the tester group → opt into testing → install from Google Play*

A tester receiving only the Play Store link may not be enough if they have not first been granted access and opted in correctly.

4. Confirm that testers actually joined

Do not assume that someone who said “I’ll test it” has completed the enrollment process.

Check your Play Console and keep track of who has actually opted in.

5. Keep the test running

Once enough testers are enrolled, avoid unnecessary interruptions.

Remember that the relevant testers need to remain continuously opted in for the required period.

Where can you find 12 Android testers?

This is usually the hardest part for indie developers.

Google suggests starting with your personal and professional network, including friends, family, colleagues, classmates, and communities where potential users may be found. (Google Support)

In practice, you can try:

• Friends or coworkers with Android devices
• Developer communities
• Indie hacker communities
• Reddit or Discord groups
• Local developer groups
• People interested in the category of your app
• Reciprocal testing communities

The challenge is not simply finding 12 people once.

You need testers who understand what they need to do and are willing to remain enrolled long enough for the test to count.

Use reciprocal testing instead of repeatedly asking for favors

That is the problem TesterGround is designed around.

TesterGround is a community where Android developers can discover apps that need testers and help each other through the closed-testing process.

Instead of posting your link and waiting for strangers to help you, the basic idea is:

1. Find another Android app that needs testing.
2. Join its test.
3. Complete the access and installation steps.
4. Test the app and provide useful feedback.
5. If you have your own published testing request, ask the developer to test your app in return.

This turns tester recruitment into an exchange between developers rather than a one-sided request.

Find Android testers →

Do testers have to open the app every day for 14 days?

Google's published requirement focuses on testers remaining opted into the closed test continuously for the required period.

TesterGround therefore does not treat “open the app every single day” as a default requirement.

That does not mean engagement is irrelevant.

Closed testing should still involve real use, meaningful feedback, and enough testing for you to understand whether your app is ready for production.

What feedback should you collect?

You do not need a complicated QA system.

A small amount of structured feedback is often much more useful than dozens of generic comments.

Ask questions such as:

• Was anything confusing?
• Did any feature fail?
• Was it clear what to do after opening the app?
• Was there anything unexpectedly slow or difficult?
• What would you change before release?

TesterGround separates feedback about the app from whether another developer kept their testing commitment, so app quality and community reliability are not collapsed into one score.

Before applying for production access

Use the end of your closed test as a release-readiness review.

Check:

• Are at least 12 eligible testers still opted in?
• Have the relevant testers remained enrolled continuously for at least 14 days?
• Did testers actually install and try the app?
• Did you collect useful feedback?
• Did you fix important bugs?
• Can you explain what you learned from testing?
• Can you explain why you believe the app is ready for production?

When you apply, Google may ask about your testing process, the feedback you received, changes you made, and how you determined that your app was ready. (Google Support)

Common mistakes

Recruiting exactly 12 testers

One tester leaving can put you below the minimum. Having a buffer is safer.

Sending only the installation link

Make sure testers complete the full access and opt-in process.

Waiting until the last day to check progress

Monitor enrollment throughout the test.

Treating closed testing as a checkbox

The 14 days are an opportunity to discover problems before real users do.

Assuming 14 days automatically means approval

Completing the requirement makes you eligible to apply. Google still reviews the production-access request.

Closed testing checklist

• Confirm whether the requirement applies to your developer account.
• Prepare a stable test build.
• Create the closed testing track.
• Configure your tester group.
• Recruit at least 12 testers — preferably a few more.
• Send clear group, opt-in, and installation instructions.
• Confirm that testers actually opted in.
• Keep enough testers continuously enrolled for at least 14 days.
• Collect useful feedback during the test.
• Fix important issues and document what changed.
• Review your production readiness.
• Apply for production access in Play Console.