How to Find 12 Testers for Google Play Closed Testing

For affected new personal developer accounts, at least 12 testers must remain opted in to the closed test for 14 consecutive days before the developer can apply for production access.

The difficult part is not collecting 12 names. It is finding participants who can meet all of the following conditions:

• Opt in with the correct Google account
• Install the app from Google Play
• Remain in the test for 14 days
• Actually use the app
• Share bugs and usability concerns

Do not recruit exactly 12 people

If you ask only 12 people, a single dropout or account mismatch can reduce the active count below the requirement.

A safer initial target is:

A buffer is useful because participants may:

• Never open the participation link
• Use a different Google account from the one registered
• Have an unsupported device
• Leave the test before the period is complete
• Misunderstand what participation requires

Option 1: Ask people you know or existing users

Friends, family members, professional contacts, and existing users can be the first candidates when those relationships are available.

You do not need to ask them to spend hours in the app every day. Explain the essential requirements clearly:

1. This is a Google Play closed test
2. They must open the link with the specified Google account
3. They need to install the app and check its main functions
4. They should not leave the test for 14 days
5. They should share anything that is broken or confusing

Example recruitment message

I am looking for testers to help with a Google Play pre-release test of an Android app.
Please join through the participation link, install the app, and check its main features.
Please remain enrolled in the test for 14 days and let me know about any bugs or unclear interactions.

Option 2: Arrange mutual testing in developer communities

Independent-developer communities sometimes organize mutual testing in which participants check one another’s apps.

Do not turn mutual testing into a simple exchange of names. A useful request should:

• State the target OS and device conditions
• Share the correct opt-in URL
• Limit the requested checks to three to five important features
• Explain the joining deadline and required participation period
• Define what you will do in return

See What Is Mutual Testing? Benefits and Precautions for a more detailed explanation.

Option 3: Use TestCrew

TestCrew helps app developers organize mutual test participation.

Developers can earn credits by testing other apps and use those credits to recruit testers for their own app. This creates a recruitment path even when personal connections are limited.

Prepare the following information before listing an app:

• App name
• Supported Android conditions
• Opt-in URL
• Features to test
• Testing precautions
• Recruitment period

See What Is TestCrew? How It Works for the complete flow.

Check the complete joining flow before recruiting

Before inviting people, use a separate account or a dedicated tester account to verify the participant experience yourself.

Checklist

• The closed-test release is published
• The opt-in URL opens
• The invited account can join
• The user can reach the Play Store installation page
• The latest build can be installed
• The app does not fail critically on first launch
• Sign-in and the main features work

If recruitment starts while the link is broken, many testers will stop at the same point.

Track each participant’s status

As the group grows, it becomes difficult to remember who completed each step. Track at least the following fields.

Do not rely only on the tester count shown by Google Play. Keeping the participant’s own completion report makes troubleshooting easier.

Recruitment messages that often fail

Avoid requests that say or imply:

• “You only need to click the link”
• “You do not need to install the app”
• Nothing about what should be tested
• Nothing about the 14-day participation period
• Unclear return-testing expectations
• No explanation of the app or required permissions

When testers do not understand what completion means, they may join and then do nothing, or leave the test partway through.

Summary

When recruiting 12 testers, focus on designing participation that can remain stable for 14 days, not simply on reaching a number.

1. Recruit about 14 to 16 people to allow for dropouts
2. Track opt-in, installation, and functional checks separately
3. Confirm that each person uses the correct Google account
4. Give specific features to test
5. Explain that testers should not leave during the required period
6. Use mutual testing or TestCrew when personal contacts are not enough

Next, share What Testers Should Do During the 14-Day Closed Test with participants.