Back to blog
Google PlayAndroid

Find testers for Google Play: the 12-tester rule and a 20-tester plan

Understand Google's minimum, prepare access, and choose a managed testing plan without confusing a service guarantee with production approval.

By TesterSplayFebruary 9, 20262 min read
Find testers for Google Play: the 12-tester rule and a 20-tester plan

Start with the rule, not the sales pitch

For personal developer accounts created after November 13, 2023, Google requires at least 12 testers to remain opted in continuously for 14 days before applying for production access. Check the requirement displayed in your own Play Console. Having 20 testers is not Google's universal minimum: it can be the coverage offered by a testing service.

An invitation, a downloaded APK, and a completed opt-in are different things. Before recruiting anyone, publish a working build to the closed track, configure eligible accounts and countries, and test the participation link with an authorized Google account.

Prepare the app before inviting testers

  • Supply the closed-test opt-in link, not only the public store URL.
  • Wait until access changes are approved and published; “in review” is not available to testers yet.
  • Provide a dedicated app login when needed, without sharing your developer account or real customer data.
  • Explain the main workflows, where feedback should go, and how paid features can be tested safely.

Ask one eligible tester to complete the entire journey: open the invitation, opt in, install, sign in, and use the core feature. Resolve access failures before onboarding everyone else.

What TesterSplay currently offers

The Basic Managed plan costs US$15 and coordinates 12 testers for 14 days, with instructions, private chat, and a second attempt if coverage is insufficient. The Guaranteed plan costs US$30 and includes 20 testers, replacement of inactive participants, and priority coordination. These are one-time prices per app, not recurring subscriptions.

The current offer is managed testing. Old references to free cross-testing or earning money as a tester do not describe a service currently offered by TesterSplay. The testing period starts when access works and testers join, not on the payment date.

Finish with real feedback

Document the features tested, issues reported, fixes shipped, and checks performed after those fixes. Answer the production-access questionnaire from this actual history. Do not manufacture sessions, reviews, screenshots, or questionnaire answers. Google decides whether the app is ready; neither a tester count nor a paid plan guarantees publication on a specific date.

Compare the current plans or check your participation link.

Source: Google's testing requirements.

Share this article