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.

What happens if a tester drops out during Closed Testing?

The short answer

If a tester drops out and your active count falls below 12 on any day, Google can reset the 14-day counter to zero. The days you already completed don't carry forward — you start the 14-day window over.

Why a single drop-out is so costly

Google measures 12 unique testers active every consecutive day. The moment a day closes with only 11 active testers, the streak breaks:

Day 1-8: 12 active  ✓ (8 days banked)
Day 9:   tester quits → 11 active  ✗
Result:  counter resets — those 8 days are gone

This is why drop-outs, not recruitment, are the real risk to your timeline.

How to recover

Detect fast. Watch daily activity, not just sign-ups. You need to know a tester went quiet that same day.
Replace before the day closes. Add a fresh active tester so the day still ends with 12 active.
Keep spares. Maintain 2-3 standby testers ready to step in immediately.
If the streak already broke, restart cleanly with a full 12 from day one — don't try to patch a broken window.

The realistic drop-out rate

Even with engaged testers, expect roughly a 10-15% chance that someone drops out for personal reasons during 14 days. Plan for it; don't assume all 12 will finish.

How TestHive handles drop-outs automatically

TestHive monitors daily check-ins and auto-queues a replacement tester within 24 hours of a drop-out, so your active count never closes a day below 12 — the 14-day streak keeps running instead of resetting.

Perguntas frequentes

Q: What happens if a tester quits during Closed Testing?

A: If their drop-out pushes you below 12 active testers on a given day, Google can reset the 14-day requirement. Days already completed do not carry forward — you start the 14-day window again.

Q: Can I add a replacement tester mid-window?

A: Yes. Adding a new tester to keep 12 active is allowed. The key is timing: replace fast enough that you never close a day below 12 active testers.

Q: Does one inactive day really reset everything?

A: If it drops you below 12 active testers, yes — the continuous 14-day streak is what Google measures, so a single sub-12 day breaks it.