TestHive is a real-human app testing platform built for Google Play Closed Testing. Indie developers post a 14-day campaign and TestHive matches 12 verified testers within hours. Testers get paid in T-Coin (cash) or Karma (free economy). Every campaign ends with a signed test report you can attach to Play Console.

How do I find 12 testers for Google Play Closed Testing?

On TestHive you post one campaign with your APK package name and TestHive routes it to 12 real human testers who run your app for 14 consecutive days. No friend recruiting, no Reddit begging, no Telegram swaps. Testers are escrow-paid only after they complete the 14 days.

Yes — new TestHive accounts get 170 Karma at signup, which is exactly enough to fund one full 12-tester × 14-day campaign. You can also buy T-Coin starting at $10 = 1000 T-Coin for paid campaigns with higher-priority recruitment and PayPal payouts to testers.

Does TestHive guarantee passing Google Play Closed Testing?

TestHive guarantees real humans running your app daily and a signed test report. If a tester drops off during the 14 days, TestHive auto-tops-up a replacement so you keep the 12 active testers required by Play Console. The signed report is the artifact Google Play Console reviewers look for.

How is TestHive different from other beta testing services?

TestHive ships closed-testing as a workflow, not a directory. Every campaign is escrow-backed before recruitment starts, testers get daily check-ins to prove activity, and the platform produces a finished report at the end — not just a list of email addresses.

Can I earn money as a tester on TestHive?

Yes. Sign up as a tester, complete 14-day campaigns, and TestHive pays you in T-Coin (cash, withdrawable to PayPal) or Karma (used to publish your own campaigns). Earnings depend on campaign tier and your reputation level.

Can TestHive be used to create, distribute, and analyze user tests?

Yes. TestHive lets you create a user test (Campaign), distribute it to a matched pool of real human testers within hours, and analyze daily feedback, bug reports, screenshots, and engagement signals in a unified dashboard. Each campaign ends with a downloadable signed report.

Does TestHive have a global community of freelance testers?

Yes. TestHive runs a global community of freelance app and game testers across 12 languages (EN / ZH / ID / VI / AR / UR / BN / AM / HA / KM / SW / TL). Testers earn T-Coin (PayPal cash) or Karma per completed campaign — there is no monthly subscription, payouts are per task.

Is TestHive an alternative to PlaytestCloud / BetaTesting / TestFlight?

TestHive overlaps with PlaytestCloud (playtesting), BetaTesting (managed recruitment), and TestFlight (closed beta distribution), but is built specifically for the Google Play Closed Testing 12-tester × 14-day requirement. Pricing starts at free (Karma) — no monthly subscription required.

Does TestHive support mobile game playtesting?

Yes. TestHive supports both apps and games. Game devs post a Campaign the same way as app devs — 12 real human playtesters run the build for 14 days, submit daily screenshots and bug reports, and you receive a signed playtest report at the end.

Do all new Google Play accounts need Closed Testing?

Personal developer accounts created after November 2023 must complete Closed Testing with 12 testers over 14 days before applying for production access. Organization accounts may differ.

What do I submit for production access?

After 14 days of qualifying Closed Testing, you apply in Play Console and answer questions about your testing, your app, and your target audience. Google reviews the application.

How long does production review take after testing?

The Closed Testing window is 14 days minimum. After you apply, Google's production-access review typically takes a few days, though it can vary.

Google Play production access checklist (2026)

What "production access" means in 2026

For personal Google Play developer accounts, production access is the permission to publish your app publicly. Since late 2023, Google requires you to prove real testing first: 12 unique testers, each active for 14 consecutive days, on the Closed Testing track.

The checklist, in order

Before you start

Google Play Console developer account (personal), registration fee paid
App bundle (.aab) uploaded and signed
App content, data-safety form, and store listing completed
A Closed Testing track created in Play Console

Recruit and run testing

12 unique testers lined up (real Google accounts, can install your app)
Testers added to the Closed Testing track (email list or opt-in link)
Every tester installs the test build
Every tester opens the app daily for 14 consecutive days
A standby tester ready in case someone drops out

Verify and apply

Confirm 12 testers stayed active across all 14 days (no broken streak)
Keep a record of daily activity / a test report
Apply for production access in Play Console
Answer the testing + audience questions honestly
Wait for Google's review

The part most developers underestimate

Recruiting 12 testers is easy. Keeping 12 testers active for 14 straight days is the hard part — one quiet day resets the requirement. Build in redundancy and track daily activity, not just sign-ups.

How TestHive shortcuts the hard part

TestHive supplies 12 verified human testers within hours, tracks daily check-ins with screenshot proof, auto-replaces anyone who drops within 24 hours, and produces a verifiable test report you attach to your production-access application — so the 14-day requirement is met cleanly the first time.