FAQ
Questions? Answered.
30 straight answers about Google's closed-testing rule, how we run your test, pricing and refunds. Search below or pick a topic.
Google's requirement
Google requires developers with newly created personal Play Console accounts to run a closed test before they can apply for production access. The test needs at least 12 testers who have been opted in continuously for at least the last 14 days. Google may also look at how engaged testers were and at your answers about the test when you apply.
No. The requirement applies to newly created personal developer accounts. Organisation accounts are generally not affected. Check the Dashboard in your Play Console: if you need to complete a closed test, Google shows it there.
A tester joins your closed test using the opt-in link and stays joined. If a tester leaves the test, they stop counting toward the continuous period. Our testers are our own team, and they stay opted in for your whole testing window.
You can, but keeping 12 people opted in every day for 14 days is harder than it sounds, and one person leaving early can restart your count. Our testers do this as their job: they stay in for the whole window, use your app daily and write real feedback.
No. The requirement is about getting production access for an app. Once production access is granted, normal updates don't need another 14-day closed test.
Getting started
A Google Play developer account, your app uploaded to a closed-testing track in Play Console, and our Google Group added as testers on that track. That's all. You don't need any testers of your own.
About 10 minutes: a few minutes in Play Console to turn on closed testing and add our Google Group, and a couple of minutes on App12Testers to add your app. We do everything after that.
Instead of typing 12 or more Gmail addresses, you add one Google Group email to your closed-testing track (Testing, then Closed testing, then Manage track, then Testers). Our testers are members of that group. Each tester still opts in to your app individually. Adding the group doesn't opt anyone in automatically.
In Play Console, open your closed-testing track and go to the Testers tab. Google shows the link testers use to join (the opt-in URL). Copy it and paste it into App12Testers when you add your app. It only works after you've published a release to that track.
We check your setup, usually within a day: we open your opt-in link, match the package name and confirm our group can see the test. If something's off, we tell you exactly what to fix. Once it's right, we assign your testers.
Yes. One testing credit covers one app, so buy one credit per app. Each app gets its own testers, dashboard and report.
During the test
The clock starts when every tester on your plan has joined your closed test, not when you pay. That way no testing day is wasted, and your dashboard shows the real start date.
They install your app on their own Android devices, explore its main features over the testing window and send structured feedback: crashes, usability problems, compatibility issues and missing functionality. They don't write public reviews or ratings for you. Google prohibits incentivised ratings and reviews.
Real people from our own vetted team, each using their own Android phone and their own Google account. They're invited by us, not recruited from the public, and they test as their regular work.
Some of it is reported by testers themselves, like joining the test, installing the app and checking in. We label it that way on your dashboard and back it up with structured feedback and admin review. Your Play Console remains the authoritative source for opt-in counts.
Yes. Your dashboard shows how many testers have joined, installs, the current testing day and the feedback as it comes in.
Yes. Publish new builds to the same closed-testing track as usual and testers get the update through Google Play. Keep the same track so the opt-in link and the testers' continuous count stay intact.
No. Testers never post public ratings or reviews for your app as part of their work. Their feedback goes to you privately, in your dashboard and final report.
Feedback appears on your dashboard during the test. When the window ends, we publish a final report with all of it in one place, under Reports in your account.
Pricing & payments
Basic is ₹499 for 12 testers over 14 days, Standard is ₹899 for 14 testers over 16 days, and Premium is ₹1,499 for 19 testers over 21 days. Each is a one-time payment, with no subscription. One payment gives you one testing credit for one app, and you can use it any time within 12 months.
Each payment gives you one testing credit for one app. Use it whenever your app is ready: it stays valid for 12 months and keeps the plan you bought, even if prices change later.
Basic covers exactly Google's 12 testers for 14 days. Standard adds more testers and days for a comfortable safety margin, and it's our pick for most apps. Premium gives the most testers, the longest window and priority support.
No. You pay once per app. There's nothing recurring and nothing to cancel.
By UPI, debit or credit card, or netbanking, through a secure checkout. You get a PDF invoice for every payment in your account.
Guarantee & refunds
Nobody can promise approval, because Google decides that independently, so be wary of anyone who claims otherwise. What we do promise: if Google doesn't grant production access after your completed test, we'll run the test again for free or refund you in full. Your choice.
Send us Google's response through a support ticket. You then choose: we run your test again for free, or we refund you in full.
Unused testing credits aren't refundable, but they stay valid for 12 months. Once you've used a credit on an app and we haven't started work, yes. Once testing has started, refunds depend on the work already delivered. If we can't supply the promised testers, we'll offer an extension or a refund. And if Google doesn't grant production access after your completed test, you can choose a free re-run or a full refund. See our refund policy for the details.
Account & support
Open a support ticket from your dashboard, or email us. A real person reads every message and replies.
Only what they need to test it: the app name, your description, what to focus on and the opt-in link. They never see your payment details or account information.
Our tester team is invite-only. If you'd like to join, send us a message through the contact page and tell us about the Android phones you use.
Official reference from Google:Google Play app testing requirements
Still have a question?
Ask us. A real person replies.
About your app, your Play Console setup or anything else.

