How TestHive works (in short)
TestHive turns Google Play's Closed Testing requirement into a guided 7-step flow. You bring the app; TestHive brings 12+ verified testers and the daily tracking that keeps the 14-day window intact.
The 7 steps
- Connect Google Play Console. Sign in (Google OAuth or magic link). TestHive verifies your developer identity.
- Submit your app. Provide the package name and your Closed Testing track URL. TestHive verifies the app exists and you can invite testers.
- Pick a payment type. Karma (free — 170 at signup covers one campaign) or T-Coin (paid — $10 → 1,000 T-Coin, faster recruitment).
- Launch the campaign. Recruitment starts within minutes for paid, hours for free. Testers join, install your app, and begin the 14-day run.
- Testers check in daily. Each tester uses the app and submits a screenshot per day — the verifiable proof of daily activity.
- Triage and respond. Review daily feedback and bug reports, award bonuses for high-quality reports, reply for clarification.
- Auto-settle on day 14. Once 12 testers complete 14 consecutive days, the campaign settles and you download a verifiable test report.
What keeps the 14-day streak alive
Google resets its counter if active testers ever drop below 12 on any day. TestHive prevents that with:
- Daily check-ins (screenshot proof), so a quiet tester is detected the same day.
- Auto-replacement within 24 hours, so the active count never closes a day below 12.
- Anti-fraud monitoring that keeps bot/farm accounts out, so your report passes Google's review.
After the campaign
You attach the verifiable test report to your Play Console production-access application. See What is TestHive? for the big picture, or the production access checklist for the full submission path.