Frequently asked questions
Everything about the 12 testers / 14 days requirement, credits and verified testing.
Google Play
Google Play requires personal developer accounts created after November 13, 2023 to run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before production access can be requested. TestersZone helps you find those testers by swapping tests with other developers.
Google's published requirement applies to newly created personal developer accounts. Organization accounts are not covered by that specific rule, but always check your own Play Console, since Google can change its policies.
No. The requirement is about a closed testing track. Testers on an internal test track do not count, so create a closed test and share its opt-in link with your TestersZone testers. Our guide on internal vs closed vs open testing explains the differences.
Per Google's help page, testers who opt in and then opt out before 14 days do not count toward the requirement. That is why TestersZone gives each app up to 20 seats, 8 more than the 12 required, and penalises testers who leave early.
No. TestersZone is an independent community. We cannot guarantee that Google approves your production access application. Google reviews your test and your answers to its questionnaire separately.
Credits
You get 15 credits when you sign up. Each app you test pays 15 credits for the first verified day, 2 credits for each following day, and 22 credits on day 14 (61 credits per completed app).
During our launch, your first app listing is free. After that, each listing costs 60 credits: your 15 welcome credits plus the first day of three apps (3 × 15) gets you there, or one full 14-day test run.
Yes. Leaving a test early costs 15 credits, and being removed by a developer for faking a test costs 20 credits plus a strike. Three strikes block you from joining new tests.
Paid credit packs and a priority listing plan are coming soon. Open the pricing popup to join the early-access list. The free community plan stays free.
Testing
Every daily check-in is checked by server-side security rules. The tester must start a timed session at least 60 seconds before checking in, can check in only once per app per day, must write at least 20 characters of feedback, and, if you enable it, must enter a secret code that only appears inside your app.
On your app page in the dashboard you can copy every tester's Google Play email as a comma-separated list and paste it into an email list in Play Console. You can also use a Google Group, in which case testers join the group from your opt-in link.
Up to 8 active tests at a time. A slot frees up when you finish all 14 days or leave a test.
Account
Yes. Google counts testers who opt in with a Google account and install from the Play Store, so you need a real Android device signed into the Google account you register as your tester email.
Yes. The community plan is free forever: you pay with your time by testing other developers' apps.
Still stuck? Read the guides or contact us.