Frequently asked questions
What exactly does Google Play require?
Personal (individual) Play Console developer accounts created after November 13, 2023 must run a closed test before they can publish to production. Google's stated requirement is at least 12 testers opted in to the closed test, continuously, for the last 14 days before you apply for production access. Testers must be opted in — merely being invited doesn't count. Organization accounts are not subject to this requirement.
Does passing the 14 days guarantee production access?
No, and be suspicious of anyone who says otherwise. After the closed test, you apply for production access and answer questions about your testing; Google evaluates the quality of your test — including whether testers were engaged and whether you iterated on the app. TesterWiz ensures the testing genuinely happened with real humans and gives you evidence of it. The decision remains Google's.
Why do testers submit their Google email, and why do I verify it?
Opted-in testers appear in your Play Console (or your Google Group). Each TesterWiz tester registers the exact Google account they'll opt in with; you check those emails off against your own console before the 14-day clock starts. This closes the classic fraud loop where a 'tester' claims participation you can't verify.
What if a tester uninstalls or goes silent mid-test?
Their missed check-ins are visible to you in real time on the campaign's day rail. Testers who skip any required screenshot check-in (days 3, 7, and 11) are automatically flagged at confirmation and not credited until an admin reviews the evidence. You can also dispute individual testers yourself — a human admin decides either way. Testers who drop mid-campaign hurt their public rating and forfeit the credit.
Is TesterWiz really free? What's the catch?
Genuinely free — there is no payment anywhere in the product: no cards, no checkout, no payout details. It runs on a credit exchange instead. Every new account spins a one-time wheel for its starting credits (18 or 36). After that, you earn 3 credits for each app you test — 1 the moment you submit each early check-in, the last when the developer confirms — and 36 credits posts your campaign (or 18 starts one half-down, with the remaining seats unlocking as you earn). The 'price' of testing is testing back.
How do credits work?
Testing one app for the 14-day window earns 3 credits (a seat's full value); posting a campaign costs 36 — exactly the 12 tester-seats it consumes, which keeps the exchange fair. Your first three completed tests pay a double bonus, and when testers are scarce completions pay extra on top. New testers run 3 apps at once; reliable testers unlock 5, then 7 — so earning a full campaign typically takes two to three 14-day windows. Credits are non-transferable and have no cash value.
Can one account be both a developer and a tester?
Yes. Roles are contextual, not exclusive — the same account can run campaigns and test other people's apps. You can't test your own campaigns, and self-dealing patterns are surfaced on our fraud dashboard.
What does the 14-day clock actually track?
The campaign starts when the developer has verified 12 opt-ins. A daily job advances the day counter; testers submit screenshot check-ins on fixed days (3, 7, 11). On day 14 the campaign moves to confirmation. Note that Google's own 14-day window is measured by Google — keep your testers opted in until Google grants production access, not just until our clock ends.
Is this against Google's policies?
Google requires real testing by real people — that is exactly what TesterWiz provides and verifies. What violates policy is fake engagement: bots, incentivized installs that misrepresent usage, or review manipulation. Our testers are fellow developers earning credits for verified participation in your closed test; we never touch ratings or reviews, and we require testers to genuinely use the app. That said, compliance with Play policies is ultimately the developer's responsibility — read Google's current guidance before you apply for production access.
What if I cancel a campaign?
While your campaign is still recruiting you can cancel it yourself from the campaign page and every credit comes back instantly. Once the 14-day clock starts, contact us and an admin can return the credits if the campaign can't run. Once a campaign completes and testers are credited, those credits are spent. Individual tester disputes never auto-refund — they go to human review.