Personal accounts after Nov 13, 2023
12 testers, 14 days: we meet Google Play's requirement for you.
Google Play Console requires new personal developer accounts to run a closed test before publishing an Android app. We run that test for you, and you follow every day in your dashboard.
If the 14 days aren't completed, you get your credit or your money back.
What is the Google Play 12 testers requirement?
To apply for production access on Google Play, your app's closed test needs at least 12 testers who stay opted in for 14 days in a row. The requirement applies again to every new app.
- Who it applies to
- Personal developer accounts created after November 13, 2023
- Number of testers
- At least 12 opted-in testers. It was 20 when first announced and was lowered to 12 in December 2024.
- Duration
- 14 days in a row. A tester who leaves the test and rejoins starts over.
- Which track counts
- Closed testing only. Internal testing doesn't count.
- Organization accounts
- The requirement is defined only for personal accounts; it doesn't apply to organization accounts.
- Once you meet it
- You can apply for production access. Google's review usually takes 7 days or less, but can occasionally take longer.
Current requirement: Play Console Help, App testing requirements for new personal developer accounts. Last checked: .
You share the link, we run the 14 days.
If your closed test release is live in Play Console, setup takes a few minutes. If not, start with the guide to setting up a closed test.
-
One test uses one credit. Credits never expire; use them whenever you like.
Credits41 credit = 1 test- 1 credit1 app
- 5 credits5 apps
- 10 credits10 apps
Buy creditsCredits never expireUse them anytime -
In Play Console, add our Google Group on your closed test's Testers tab and paste the opt-in link into your dashboard. We never ask for your Play Console password.
SetupGoogle Group addresstesters@testerpass.exampleOpt-in linkplay.google.com/apps/testing/com.exampleI added the group to the closed testLink savedStart testOpted-in testers0 / 15, waiting -
The 14-day clock starts when the twelfth tester opts in. Each one opens your app at least once a day, and your test table fills in day by day. 3 backups opt in alongside them: even if one leaves the test, the opted-in count doesn't drop below 12 and the 14 days don't start over.
Test table10 / 14Today 10 / 15- T3waiting
- T6waiting
- T7opened
- T9opened
-
We let you know when the 14 days are up. Apply for production access right away: testers leave on day 15 at 11:59 PM Turkey time (UTC+3). Google decides whether your app is published.
Google Play ConsoleInbox · nowCongratulations! Your app now has production access on Google Play
Production access grantedIllustration only. Google grants approval; we meet the 14-day requirement.
See for yourself that the test is running.
The test table in your dashboard shows which tester opened your app on which day. Use the slider to fast-forward the sample table.
Day-by-day test table
If a tester doesn't open your app, you see it on the table the same day.
The same number as Play Console
Compare the opted-in tester count in your dashboard with the one Play Console shows. The two should match.
No access to your account
We never ask for your Play Console password or access permissions. The only thing you give us is your closed test's opt-in link.
Sample test table
com.example.app, closed testWhere do you find 12 testers?
There are three ways, each with pros and cons. If you have time, the free routes work; if your launch date matters, choose a managed service.
| Managed service (TesterPass) | Friends and family | Free testing communities | |
|---|---|---|---|
| Cost | $12.99 per app test | Free | Free |
| Your effort | A few minutes of setup in Play Console | Finding 12 people and reminding each of them for 14 days | Testing other people's apps to earn credits |
| When it starts | Within 24 hours of Google's approval | As long as it takes you to gather 12 people | Once you've earned enough credits |
| Tracking | Live day-by-day test table | You count in Play Console yourself | Depends on the community |
| Feedback | Feedback report from the test record, with your test data for the application form | Directly from people you know | Depends on the community |
| Most common catch | It costs money | Someone leaves before day 14 and the count drops below 12 | You can't tell who will open your app, or when |
One test, one credit.
1 credit = 1 app test12 testers14 days in a row
One-time payment, no subscription. Credits never expire. [VAT STATUS] Prices in US dollars (USD).
In every test
- 12 testers + 3 backupsEven if one leaves the test, the opted-in count doesn't drop below 12.
- 14 consecutive daysEach tester opens your app at least once a day.
- Starts within 24 hoursAfter Google approves the change that adds our Google Group.
- Live test tableSee in your dashboard which tester opened your app on which day.
- Feedback reportBased on the test record: your test data for the application form questions.
- Refund promiseIf the 14 days aren't completed, your credit is restored or your money refunded.
If 12 testers don't complete 14 days in a row within 21 days after setup is complete, we return that test's credit to your account; if you prefer, we refund its price to your payment method. Exclusions are listed in the FAQ.
Google approving your application is not part of this promise; Google makes that decision.
Frequently asked questions
About the 12 testers requirement, closed testing and production access.
What is the 12 testers rule?
It's the everyday name for the closed testing requirement Google Play introduced for new personal developer accounts. Before your app can go to production, at least 12 testers must stay opted in to its closed test for 14 days in a row.
Where do I find 12 testers?
There are three ways: people you know, free testing communities or a managed service. Whichever you choose, the testers have to opt in to your closed test and stay opted in for 14 days. The comparison table above shows how the three differ.
It used to be 20 testers. Is that still the case?
No. The requirement was 20 testers when first announced and was lowered to 12 in December 2024. The 14-day period hasn't changed. Old forum threads that say 20 are out of date.
Does internal testing count toward the requirement?
No. Only the closed testing track counts. However long you wait in internal testing, you won't be able to apply for production access.
When do the 14 days start?
On the day 12 testers are opted in to your closed test. When you apply, Google checks that at least 12 testers have been opted in continuously for the last 14 days. That's why the calculator below counts from the opt-in day.
What happens if a tester leaves the test?
A tester who leaves stops counting; if they rejoin, their 14 days start over. So the number of opted-in testers must not drop below 12 at any point during the 14 days. We start your test with 12 testers and 3 backups, so even if one leaves, the opted-in count doesn't drop below 12.
Is using a paid testing service against Google's rules?
[ANSWER BASED ON METHOD: how our method relates to what Google expects from testers, stated clearly here]
Do you need my Play Console password or access?
No. We only ask for your closed test's opt-in link. You add our Google Group to your closed test yourself; we never sign in to your account.
How soon does the test start?
Within 24 hours after Google approves the change that adds our Google Group. If you're publishing a closed test for the first time, it can take a few hours for Play Console to make the opt-in link available.
Do I need to do anything during the 14 days?
Just keep your closed test running and don't remove our Google Group from the list. You follow the rest on the test table; if anything needs your attention, we'll write to you. When the 14 days are up, apply right away; testers leave on day 15.
What if my app is paid?
Testers who join a Play Console closed test have to buy a paid app. That's why we don't accept paid apps right now.
What does the production access application ask?
There are three sections. Your closed test: where you found testers and how easy it was, how testers used your app, whether that usage matches what you expect in production, a summary of the feedback you received and how you collected it. Your app: its target audience, the value it offers and the expected number of installs in its first year. Your production readiness: what you changed based on what you learned in testing, and how you decided the app is ready. Our feedback report puts your test's data next to the closed test questions; you write the answers. Once the 14 days are up, the application helper in your dashboard shows these questions and the test record in one place; you submit the form. The application form guide walks through each question.
Is production access guaranteed once the 14 days are up?
No, Google makes the decision. Meeting the requirement lets you apply. Google's review usually takes 7 days or less, but can occasionally take longer. Our refund promise covers 12 testers completing the 14 days, not Google's decision.
What happens if Google rejects my application?
Most often Google asks you to keep testing: if fewer than 12 testers are opted in, or if it found the test usage insufficient. Policy violations and functional problems such as crashes are also reasons an application is turned down. If you want to keep testing, you start a new test, which uses one credit.
I have more than one app. What then?
The requirement applies per app. Each app runs its own closed test, and each test uses one credit. If you have several apps, you can buy credits in a pack of 5 or 10 and pay less per test.
Which payment methods do you accept, and do you issue invoices?
[PAYMENT AND INVOICE DETAILS: accepted payment methods, payment provider and invoice type, stated here]
What does the refund promise cover, and what doesn't it cover?
Setup is complete once Google approves the change that adds our Google Group and our twelfth test account has installed your app; the 21 days count from that moment. When the 14 days are up, we ask you for a screenshot of the task on your Play Console Dashboard; if you raise no objection within 3 days, the requirement counts as met. If the requirement isn't met, your credit is restored automatically; if you prefer, that test's price is refunded to your payment method (support@testerpass.com). Not covered: removing our Google Group, switching to an email list or pausing the closed testing track while the test is running, removing Turkey from the track's countries, your app being removed from Google Play or suspended, your developer account being closed, an update that makes the app impossible to install or crash on launch, and leaving your application until after the testers have left. Google's decision on your application is also outside the promise.
Work out your application date.
You can apply for production access on day 15 after 12 testers opt in. Our testers leave at 11:59 PM (UTC+3) that day; apply the same day.
Developers who finished their test with us.
In their own words: developers who completed their closed test with us.
[REVIEW: the customer's own words, 2–4 sentences]
[FULL NAME][APP NAME] [REVIEW]
[FULL NAME][APP NAME] [REVIEW]
[FULL NAME][APP NAME] [REVIEW]
[FULL NAME][APP NAME] [REVIEW]
[FULL NAME][APP NAME] [REVIEW]
[FULL NAME][APP NAME]
Closed testing guides
If you'd rather meet the requirement on your own, these guides are all you need.