TestHive
Get started

Google Play Closed Testing: the complete guide

Published 2026-06-17

TL;DR

Google Play requires every new app to complete Closed Testing — 12 unique testers daily-opted for 14 consecutive days — before allowing production release. This guide explains exactly what counts, what doesn't, and how to fulfill the requirement reliably.

What is Closed Testing

Closed Testing is Google Play's mandatory phase before production release for any new app. Google requires you to prove your app has been tested by real humans, not bots, before allowing it to reach the public Play Store.

The exact requirement

12 unique testers must be daily-opted into your Closed Testing track for 14 consecutive days. "Daily-opted" means each tester opens or interacts with the test version on each of those 14 days. If you drop below 12 on any day, the 14-day counter resets to zero.

Why this requirement exists

Google introduced the 12 × 14 rule in late 2023 to combat fake-tester farms. Before this, developers could run quick "fake" testing rounds with paid bot accounts. The 14-day continuous activity window is hard to fake without genuine human engagement.

Common rejection reasons

  • Fewer than 12 unique testers — duplicates, family members on the same device fingerprint, or sock-puppet accounts all fail Google's de-duplication.
  • Inactive testers — testers who opt in but don't open the app daily break the streak.
  • Mismatched testing_url — if your app's package_name or testing URL changes mid-window, Google may invalidate progress.
  • Region or device restrictions — if your testing track restricts geography but your testers fall outside, they don't count.

How TestHive solves this

Every TestHive Campaign matches you with 12 real human testers who:

  • Pass a 4-gate fraud check (unique package + fingerprint + Play Scraper + super_admin oversight)
  • Get incentivized to maintain daily activity (T-Coin / Karma payment tied to daily check-ins)
  • Submit verifiable screenshots each day for audit

When the 14-day window completes, you receive a tamper-proof PDF report with SHA-256 verification — this report is what you submit alongside your Google Play production release request.

Frequently asked

  • Q: How many testers does Google Play Closed Testing require?

    A: 12 unique testers, each opted in for the testing track, with continuous daily activity tracked across 14 consecutive days.

  • Q: Do testers need to be in different countries?

    A: No. Google measures daily opt-in count, not geography. All 12 testers can be in the same country.

  • Q: What happens if a tester drops out mid-window?

    A: If you fall below 12 active testers on any day, Google resets the 14-day counter. This is why TestHive emphasizes tester reliability over quantity.

Related

Google Play Closed Testing: the complete guide · TestHive Docs · TestHive