Real testers when you need them. A test bot on every build.
Get through Google Play’s 12-tester, 14-day closed test, swap tests with other developers, or hire the community and our bot to hunt bugs and security issues — on Android, iOS, Windows and macOS.
No card needed. Testers earn credits they can spend on their own apps.
Two ways to test
People find what bots miss; bots never forget to test. Use one or both.
Cross-testing between developers
Join other developers’ tests, earn credits, and spend them on testers for your own app. Every day of testing is backed by proof from the device, not a checkbox.
Google Play closed test
We recruit 12 testers plus 3 spares into our Google Group, remind them daily, replace drop-outs and show you who opened your app each day of the 14.
Bug and security hunts on demand
Set a budget and a reward per severity. Testers file reproducible reports with screenshots; you accept, mark duplicates or reject, and only pay for accepted ones.
Automated test runs
Upload an APK, AAB, IPA, MSIX or DMG. The bot scans the package, installs it on a clean emulator or simulator, explores the UI and reports crashes with stack traces and screenshots.
How the 14-day closed test works
Google Play asks new personal developer accounts for a closed test with at least 12 testers opted in for the last 14 days before applying for production. TestHubHQ runs that part for you.
Add your app
Create the closed testing track in Play Console and add our tester Google Group to it. Upload the AAB here too if you want the bot.
Publish the campaign
Credits for 15 testers × 14 days go into escrow. Testers join from the TestHubHQ app and opt in through your Play link.
Testers use your app daily
The Android app reads Usage Access to prove your app was installed from Play and opened that day. Missed days are flagged; two in a row and the tester is replaced.
Apply for production
After 14 days you get the numbers Play asks about, the feedback testers sent, and a draft of the three answers in the production-access form.
The test bot
Runs on our device farm: Android emulators, iOS simulators, macOS and Windows hosts. Every run ends with findings mapped to OWASP MASVS, logs and screenshots.
Security scan
30 crManifest and entitlement checks, hard-coded secrets, cleartext traffic, exported components, 16 KB page alignment, signing, Mach-O and PE hardening.
Smoke test
5 crInstall, cold start, screenshot, check it is still alive.
Monkey
10 crThousands of random taps and swipes with a fixed seed so crashes can be replayed.
UI crawl
20 crWalks through screens, fills text fields, presses every button and records each new screen.
Maestro flow
15 crRuns your own Maestro YAML flow — login, checkout, whatever matters.
Closed-test daily run
10 crA crawl every day of a closed test, so you see crashes before your testers do.
Prices are in credits per run. Failed runs caused by our infrastructure are retried and refunded.
Where your testers come from
Google Play
Closed tracks with the TestHubHQ Google Group, or your own email list exported as CSV.
App Store
TestFlight public links; testers prove sessions with screenshots.
Microsoft Store
Package flights or MSIX sideloading; the desktop app records usage time.
macOS and Linux
DMG, PKG, AppImage or DEB downloads; the desktop app records usage time.
Pricing
Everything is paid in credits. Buy them, or earn them by testing other developers’ apps.
Free to start
50 credits on sign-up. Testing for others earns 2 credits per verified day plus rewards for accepted bug reports.
Example: one Google Play closed test
| 15 testers × 14 days × 2 credits (escrow) | 420 |
| Platform fee (10%) | 42 |
| Daily bot run (optional, 14 × 10) | 140 |
| Total | 462 – 602 credits |
Unused escrow is refunded when the campaign ends.
What we will not do
- Create fake Google accounts or let the bot pretend to be one of your 12 testers.
- Sell reviews, ratings or installs.
- Hide drop-outs: every tester and every day is in your report.
Test apps, earn credits
Install the TestHubHQ app, pick tests that fit your phone, use each app a few minutes a day, report what breaks. Credits pay for testers on your own apps.
Questions
Does this satisfy Google Play’s testing requirement?
Google asks for at least 12 testers opted in to a closed test for the last 14 continuous days. We recruit real people who opt in through your Play link and use the app; whether production access is granted is still Google’s decision, based on your answers and the quality of the test.
Why does the Android app need Usage Access?
It reads how long the app under test was in the foreground today and whether it was installed from Google Play — only for the apps you joined a test for — and sends that number as the day’s proof. Nothing else on the phone is read.
What happens if a tester stops?
After two missed days in a row they are dropped, lose reputation and a spare takes the slot. You only pay for verified days.
Can I test iOS or desktop apps?
Yes. Cross-tests and bug hunts work on every platform; the bot runs iOS simulator builds, macOS apps and Windows MSIX/EXE packages.
Who sees my build?
Only testers in your campaign (through the store) and our runners. Bot runs happen on clean, read-only emulator images that are reset after each job.