How to get 12 testers for Google Play, and keep them for 14 days
A personal Google Play account opened after 13 November 2023 must run a closed test with at least 12 testers, opted in for 14 days in a row, before it can apply for production. Below: the rule in Google’s words, the traps we hit on our own apps, and a free tracker, answer drafts and checklist. We do not sell testers.
Every claim on this page carries a tag, so you can tell what Google says from what we saw on our own apps and from what others report.
GoogleStated on Google’s own help pages, linked in the sources. Checked 27 October 2026.
Our runsWe saw it ourselves, in the closed tests of our own apps in October 2026.
ReportedSomeone else says so and we could not check it. Several of these come from companies that sell testers.
Our ruleHow we choose to work. A choice, not a requirement.
The rule, in Google’s words
- GoogleWho. Personal developer accounts created after 13 November 2023. Google’s Get started page marks the testing step “Personal accounts only”.
- GoogleHow many. A closed test with at least 12 testers who opted in.
- GoogleHow long. Opted in continuously for the 14 days before you apply. A tester who opts in, tests for less than 14 days and leaves does not count, and one who leaves and rejoins must be opted in for 14 consecutive days.
- GoogleTell them. Testers are to be told to stay opted in for at least 14 days.
- GoogleApply. In the Dashboard, Apply for production opens a form in three parts: how the closed test went, about your app, and production readiness. Leave the form before Next or Apply and nothing is saved.
- GoogleReview. Usually seven days or less. Google says more testing may be required if fewer than 12 testers were opted in or tester engagement was not enough, and that review is not a troubleshooting step: you must check policy compliance before you apply.
- GoogleWhat is missing. The page gives no number for how much testers must use the app.
Source: App testing requirements for personal developer accounts, Play Console Help, read on 27 October 2026. The page shows no update date.
What the counter shows, and what the review reads
- Our runsConsole’s Dashboard shows N testers currently opted-in until you reach 12. From the next day it shows 12 testers have currently been opted in for N days continuously. When N reaches 14 that sentence goes and the Apply for production button opens. The counter measures opt-ins, not use.
- Our runsFor our first two apps the 12th opt-in came on 12 October and the counter showed 14 days on 26 October, the date we expected. We read 13 days at 10:12 that morning and 14 days at 19:45 that evening, so look again the next morning rather than at midnight.
- ReportedCompanies that sell testers say the review also reads real installs and use: sessions, time in the app, retention. Google’s page says only engagement. See Testers Community (a paid service, August 2026).
- ReportedOne developer wrote that Fiverr testers arrived as 12 Gmail addresses in two days, 2 of them opted in and none opened the app. The post is on a competitor’s blog, onTest, July 2026. One source, treat it as a story.
Eight traps
- Our runsInternal testing is not closed testing. An opt-in to someone’s internal test is not an opt-in to your closed test. Google’s rule names a closed test.
- Our runsThe country list. On a phone in Türkiye we saw “This item isn’t available in your country” while testing another developer’s app: their track did not include Türkiye. Your testers will see it if you leave their country out. Add every country they live in before you share the link.
- Our runs“App not available for this account” on the opt-in page means the tester’s Google Group or e-mail is not on the track, or they are signed in with another Google account. We hit this as testers of other developers’ apps, and your testers will hit it on yours.
- Our runs32-bit phones. “Your device isn’t compatible with this version” was a build without 32-bit libraries meeting a phone that needs them. If your build is 64-bit only, some testers cannot install it. Ask for the phone model.
- Our runsGoogle Groups join quota. One Google account stopped joining groups after about ten in a rolling 24 hours (“over your quota limit”, 14 October 2026). Spread joins over several days.
- Our runsSwap partners forget. In a test-for-test swap the other developer must add your group or e-mail to their track. Open their opt-in link with your own account before you count the swap as done.
- ReportedEmulators. Two peer-testing communities say emulators, device farms and bots are not accepted. Google’s page does not mention them. See our rule below.
- Our ruleDo not stop at 12. People leave. We aim for 15 to 20 opt-ins and treat 12 as the floor, because the count must hold for 14 days.
How we run it
This is the sequence we used for our own apps. It is a method, not a promise: it has no approval to show yet.
- Create the closed track, publish a release, wait until it passes review, and add every country your testers live in.
- Add Google Groups to the tester list, both shared test communities and your own, so members opt in from the link without joining anything of yours.
- Ask each tester for three small tasks, not for “please test”. A task has an end: finish one lesson, record one note, change one setting.
- Swap with real developers only. You install and open their app on a real phone, they do yours, and each side sends a screenshot. Cap the open swaps at what you can keep up. We stopped at 12.
- Log every day: who opted in, who opened the app, phone model, where they came from, what they said. The tracker has the columns.
- Ship at least one update that answers real feedback. It also gives you an honest answer to the form’s question about what you changed.
- Ask testers to stay opted in and keep the app installed until the review is over.
- Read the counter every day. Apply when Console shows 14 days and the button is open, not before.
Our rule What we do not do. Google’s policy on user ratings, reviews and installs says developers must not attempt to manipulate the placement of apps on Google Play, and it names fraudulent or incentivized installs. So we do not buy testers, run emulators or bots, share Google accounts, or trade ratings for tests. Google’s testing page does not mention paid tester services. We have not used one and we do not recommend any. The paid pack we are considering would not sell testers either.
Two of our apps, day by day
These are the first two apps we sent for production access, from the log we kept. The apps are our own and are not named here.
| Date | What the log says |
|---|---|
| 11 Oct | Closed test running. 2 testers had opted in. |
| 12 Oct | 12 testers opted in. The count did not fall below 12 afterwards. |
| 13 Oct onwards | We linked shared test communities and our own Google Group to the track. By 26 October, 18 Google Groups were linked. |
| 26 Oct | Console showed 14 days. Apply for production was open on both apps. |
| 26 Oct, 20:03 and 23:40 | We sent the two applications. Console confirmed each with “Applied today”. |
| 27 Oct | Google had not answered when we wrote this page. We will add the outcome here. |
Two cautions. Most of our testers are developers from shared test communities, and our answers say so; we do not claim they use the apps like real customers. And twelve opt-ins by day two came from a network we had spent weeks building, so your count may move slower.
The free kit
- The tracker. 12 testers by 14 days as an Excel sheet and a CSV, plus a calculator for the day you can apply. Open the tracker
- The answer drafts. The nine questions of the production access form, with live character counters and examples from our own applications. Open the answer drafts
- The Console checklist. What to set before, during and after the test. Open the checklist
- If it comes back rejected. What Google says and what to change. Read what to do next
Questions
How many testers does Google Play need before production?
A personal developer account created after 13 November 2023 must run a closed test with at least 12 testers who stay opted in for 14 days in a row before it can apply for production access, according to Google’s Play Console Help.
Do the testers have to stay opted in for all 14 days?
Yes. Google says testers must have been opted in continuously for the preceding 14 days when you apply. A tester who leaves early does not count, and a tester who leaves and rejoins must be opted in for 14 consecutive days.
Can I buy testers for a Google Play closed test?
Google’s testing page does not mention paid testers, but its ratings, reviews and installs policy forbids manipulating where apps are placed and names fraudulent or incentivized installs. We do not sell or recommend testers. Real people who opt in and use the app are what the application asks you to describe.
Do I need 12 testers again for every new app?
In our own accounts every app has its own closed test and its own 14 days. Google’s page does not spell out the per-app point, but developers report that a second app needed its own testing again, so plan 12 testers and 14 days for each one.
Does an organization account skip the 12 testers rule?
Google’s Get started page marks the testing step as personal accounts only. Converting an existing personal account does not necessarily exempt the apps you already created, so check Play Console Help before you rely on it.
Evidence pack, coming
We are considering a paid pack per app: your day-by-day log turned into the nine application answers, a swap ledger with proof, and a plan for a rejection. It would not include testers. It is not for sale yet, and nothing here takes a payment.
Tell us you want it and what is hardest for you. We write once when it opens.
Sources
- Google Play Console Help: App testing requirements for personal developer accounts (the rule, the form and the review; read 27 October 2026)
- Google Play Console Help: Get started with Play Console (step 6, personal accounts only; read 27 October 2026)
- Google Play Console Help: User Ratings, Reviews, and Installs (placement and incentivized installs; read 27 October 2026)
- Testers Community (a paid tester service): Google Play closed testing requirements 2026 (August 2026; engagement claims, not checked)
- onTest (a paid tester service): How to get 12 testers for Google Play closed testing (July 2026; one developer’s account of a Fiverr order, not checked)
- Our own closed-test logs for two apps, October 2026
Day14 is an independent kit by Peak Apps Studio and is not affiliated with Google. We do not promise that any application is approved: Google decides.