How to Get 12 Testers for Google Play (Without Fake Accounts)

Short answer: start with your personal and professional network, then communities where your target users already gather, then social media. If that still leaves you short, use a service that recruits real testers. Recruit at least 15, because anyone who opts out before day 14 stops counting. Here's how to work each route.

1. Your personal and professional network

Google itself calls this the most common route: friends, family, colleagues and classmates. Send a short personal message, not a group blast. Explain that they need an Android phone, the Google account you'll add, and about two weeks of staying opted in. Ask them not to uninstall early.

2. Communities where your users already are

Google suggests going where potential users exist, such as local clubs for a fitness app or online groups for your niche. Testers who would actually use the app give better feedback, and the production form asks whether testers matched your expected audience.

3. Social media

A post with a clear ask works: what the app is, what you need (an Android phone and 2 weeks), and a sign-up form. A Google Group as your tester list lets people join without you editing emails.

4. Paid real-tester services

When your network runs out, services such as TestLancer recruit testers who opt in, install and use the app for the full period. Look for services that are clear about what they deliver, such as daily tasks and a report, and that don't promise approval.

Keeping 12 people opted in

Track every tester

Log the name, email and opt-in date in a sheet.

Give them a reason to open the app

Small daily tasks keep testers active and give you feedback to report.

Thank and update them

Tell testers when you fix something they reported. People stay longer when they see their feedback used.

What to avoid

Tester-swap groups where nobody actually uses your app, duplicate accounts you control, and anyone offering reviews or ratings. These either don't count or leave you nothing honest to write on the production form.

The official rules, in one place

According to Google's Play Console Help article on app testing requirements for new personal developer accounts:

• The rule applies to personal developer accounts created after November 13, 2023.
• You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
• Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
• The application has three parts: About your closed test, About your app/game and About your production readiness.
• Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
• Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.

Quick checklist before you apply for production access

• [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
• [ ] A buffer of extra testers in case someone drops out at the last minute.
• [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
• [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
• [ ] A list of changes you made because of the test, with version numbers.
• [ ] Working test credentials in Play Console if your app needs a login.
• [ ] Content rating, target audience and data safety answers that match the real app.
• [ ] No crashes or empty screens on the build you're about to ship.

If any box is empty, a few more days of testing usually costs less than another review cycle.

Mistakes that cost developers extra weeks

1. Recruiting exactly 12. One opt-out and you're back to waiting.
2. Running the test on the internal track. Internal days don't count toward the requirement.
3. Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
4. Tidying the tester list mid-test. Removing someone ends their streak.
5. Shipping no updates. The production readiness section asks what you changed because of testing.
6. Using friends who never open the app. Google can ask for more testing when engagement is low.
7. Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.

FAQ

Is 12 enough?

It's the minimum at the time you apply. Recruit a buffer of 15 to 20.

Do testers need to be in my country?

They need to be in a country your closed release is available in.

Do testers have to pay anything?

No. They install your app from Google Play after opting in.

Next step

If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.