Disclosure: 12Testers14Day publishes this article and sells the service it describes.
If your new Play Console account won't let you publish to production until you've run a closed test, you've probably come across "12 testers for 14 days". This article covers what Google requires, why developers get stuck on it, and what 12Testers14Day (shown on the site as "12Testers for 14 Days") does about it. It also covers what the service can't do.
Google Play's closed-testing requirement
According to Google's Play Console Help article App testing requirements for new personal developer accounts, personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Until then, Production and Pre-registration stay disabled in Play Console. Once you meet the criteria, you apply for production access from the Dashboard and answer questions about your testing, your app and whether it's ready for production.
Some details are easy to miss:
- Google describes this rule for personal accounts created after that date. Google's article doesn't apply it to organization accounts. Your own Play Console Dashboard shows whether it applies to you.
- The count is taken when you apply. At least 12 testers must be opted in at that moment, and they must have stayed opted in for the previous 14 days.
- Gaps break the streak. Google says testers who opt out before 14 days don't count, and someone who opts out and later opts back in needs 14 consecutive days.
- Meeting the numbers doesn't end the review. Google says it may ask you to keep testing if you had fewer than 12 opted-in testers or if tester engagement was too low.
Why developers get stuck
On paper the rule is simple. In practice, solo developers and small teams tend to run into the same problems:
- Finding 12 people with Android phones who will actually install a test build. Many developers don't have 12 willing Android users nearby.
- Keeping all of them opted in for 14 days. If even one person leaves early, you can drop below 12 and have to extend the timeline.
- Access problems. Common ones are the wrong Google Account, an opt-in link that isn't live yet, or a tester still enrolled in your internal test. Each of these stops someone from counting.
- Feedback you can use. The production-access questions ask how you tested and what you learned. Testers who install and never open the app give you little to write about.
What 12Testers14Day does
12Testers14Day offers Google Play closed-testing help for Android developers. You keep your app and your Play Console account. The service organizes the testers and the testing window around Google's requirement.
According to the live site, the service:
- Assigns real Android testers. The site says your app runs on real devices used by people, "not automated installs or passive accounts".
- Builds in a buffer. Each package assigns about 14 testers for about 16 days, so one dropout or a late start doesn't automatically put you below Google's 12 × 14 minimum.
- Shows participation and daily progress. You follow tester participation, access questions, daily progress and feedback from one shared workspace.
- Collects structured feedback. Testers follow your instructions, try the journeys you name, and report what they find.
- Helps with the production-access questions. The site provides templates and guidance for writing complete answers to Google's questionnaire. You can also try the free production-access questionnaire tool.
- Delivers a closeout report. At the end you get an organized record of participation, observations and next steps. The site has an illustrative sample report, which is labeled as a sample, not a customer result.
How it works
The How it works page describes four steps:
- Prepare. Choose a plan and submit your app details: the closed-test link, access instructions (including any login details testers need) and the journeys you want tested.
- Connect. Follow the setup instructions for your closed test. On the home page, the service says it provides the tester list and setup guidance you need to configure the closed track. Keep the build available and answer any access questions.
- Follow along. Use your workspace to track progress and answer questions during the window. If you publish a new build, let the service know.
- Review. Read the closeout report, decide what to fix, and then apply for production access yourself in Play Console.
Packages and pricing
These prices are on the live pricing page as of October 17, 2026:
| Package | Price (one-time) | Covers | Testers / days |
|---|---|---|---|
| Basic | $15 | 1 credit = 1 app submission | 14 verified testers, 16 calendar days |
| Premium | $29 | 2 credits = 2 app submissions | 14 verified testers, 16 calendar days per app |
| Enterprise / Custom | Ask the team | Multiple apps, dedicated coordination, custom workflow | Tailored |
You buy packages, not a subscription. Agencies or teams with several apps can contact the team about a custom plan.
What 12Testers14Day doesn't do
- It doesn't decide production access. Completing 12 testers for 14 days makes you eligible to apply. Google reviews your account, app, store listing, policy compliance and answers, and makes the decision itself. No testing service can promise approval.
- It doesn't fix the app for you. Crashes, broken builds, login walls without test credentials, or policy problems can still cause trouble. Google says production review isn't a troubleshooting step.
- It doesn't submit anything for you. You set up the closed track, publish the build and submit the production-access application.
If the service itself fails to deliver the agreed testing window, refunds follow the published service guarantee. That page explains what counts as a delivery failure and lists the exclusions (for example a wrong opt-in link, a closed track that isn't live, broken builds, or a Google rejection by itself).
How testers join your closed test
The service supplies the testers, but it helps to know how joining works. On your closed track's Testers tab, Play Console offers two access methods:
- Email list. You add testers' Google Account addresses to a list in Play Console and attach it to the track.
-
Google Group. You enter a group address (
yourgroupname@googlegroups.com). Google says only members can join, and they must join the group before opting in.
With either method, Google's test setup help says a tester counts only if they're in the track's tester configuration and have actively opted in through the opt-in link. Remember these basics as well:
- The opt-in link only appears when the app's status is Published.
- Testers need a Google Account or Google Workspace account.
- Testers in your internal test aren't eligible for the closed test until they leave the internal test.
When a tester is blocked, work through the checks in Invite testers and fix access problems.
FAQ
Do organization accounts need 12 testers for 14 days?
Google's help article describes the requirement for personal accounts created after November 13, 2023. Check your Play Console Dashboard to see what applies to your account.
Does the service guarantee production access?
No. Google alone makes that decision.
Can I find testers myself instead?
Yes. Google recommends personal and professional networks and communities. The site also runs a free, self-managed tester community if you'd rather coordinate the test yourself.
What should I prepare before buying?
You need a closed track with a published build, a working opt-in link, test login details if your app requires sign-in, and a short list of the journeys you want tested. The closed-testing checklist covers these.
Get started
If you'd rather spend the next two weeks on your app than on recruiting testers, review the packages and pricing or read how a testing run works. Then register your app on 12Testers14Day.
Official references: App testing requirements for new personal developer accounts · Set up an open, closed, or internal test
Top comments (0)