12+ TESTERS · 14-DAY CLOSED TESTING
Google Play wants at least 12 testers opted in for 14 consecutive days before your production track unlocks. We run that whole window for you: 12+ real testers on real Android devices, installing and opening your app every single day, with the proof landing in your dashboard as it happens. No chasing, no spreadsheets, no missed day.
From $14.99 · Starts in 4-6 hours · Money-back guarantee
Real testers, real devices Installed & opened today
Tap the board to see the real result
REAL RESULTS
Two real Play Console screens, 14 days apart. On the left is the wall every developer starts at — “12 testers have currently been opted in for 1 day”, button greyed out. On the right is what our testers' 14 days unlock. 1,700+ apps approved and counting.
PART 1 · DAY 1 OF 14
The checklist is waiting on your dashboard: release published, 12 testers opted in, and 1 day counted. Production access stays locked until the test has run 14 consecutive days — this is the part we take off your hands, every day, without you chasing anyone.
PART 2 · DAY 15
Same checklist, all green — and the greyed-out button is replaced by “Congratulations! Your app has been granted Google Play production access.” That is what the 14 days buy you: the production track, open.
VIDEO GUIDE
Two short walkthroughs from our own channel: setting the closed test up before the clock starts, and what to do the day the 14 days are done.
SETUP · 14 DAYS · PRODUCTION ACCESS
VIDEO 1 · BEFORE YOU START
Add the 12 tester emails we send you to a closed track, publish the release and share the invite link — the seven minutes of clicking that starts the 14-day clock.
VIDEO 2 · AFTER THE 14 DAYS
Day 14 is done and the streak is complete. Here is the production-access application in the order Google asks for it, plus the questionnaire answers that pass review.
PRICING
No subscription — one flat payment, no hidden fees. Every plan runs the full 14-day closed test; if Google does not approve, you choose a free retest or a full refund.
12 testers · 14 consecutive days
One-time price: $14.99
Lowest price
≈ $1.25 per tester · one-time payment
Get 12 testersMoney-back guarantee · no subscription
MOST POPULAR · 20% OFF
20 testers · 14 consecutive days
One-time price: $19.99
Regular price $24.98
Save $4.99
≈ $1.00 per tester · one-time payment
Get 20 testersMoney-back guarantee · no subscription
DONE FOR YOU
Full-service plan · we run it for you
One-time price: $24.99
Regular price $31.23
Save $6.24
One-time payment · we handle the whole process
Start the Enterprise planMoney-back guarantee · no subscription
Secure payment with Stripe Card details are handled by Stripe — we never see or store them. VisaMastercardAmexApple Pay
100% money-back guarantee
If your app is not approved after our testing, you get a full refund. No questions asked.
CLOSED TESTING 101
Google's 12-tester, 14-day requirement applies to personal developer accounts created after November 13, 2023. Eligible developers must meet the applicable testing requirements before applying for production access. Meeting the minimum testing period does not guarantee approval.
Understand who must complete the 12-tester requirement and when it applies.
For personal Google Play developer accounts created after November 13, 2023, Google requires a closed test with at least 12 testers opted in continuously for at least 14 days before the developer can apply for production access. Check your account type and creation date against Google's current rules. Completing the minimum period makes you eligible to apply; it does not guarantee approval.
Read the full guide: How to Get 12 Testers for Google Play Closed Testing →Understand why account type and creation date matter.
Google's 12-tester, 14-day requirement specifically identifies personal developer accounts created after November 13, 2023. Do not assume every personal or organisation account follows the same eligibility path. Check the current Play Console requirements for your own account before planning a campaign.
Read the full guide: Why Does Google Play Require 12 Testers? →Learn the difference between internal testing, closed testing, open testing, and production.
Internal testing is designed for quick distribution to a small group, with up to 100 testers. Closed testing lets you distribute a release to a selected group. Open testing makes a test available to a broader audience when the account is eligible. Production is the public release track. For eligible new personal accounts, the closed-testing requirement must be met before applying for production access.
Read the full guide: Google Play Closed Testing vs Internal Testing →Prepare your testing track, release, tester list, and feedback channel.
In Play Console, open your app and navigate to Test and release, then Testing, then Closed testing. Configure the track, prepare and roll out a test release, choose an email list or Google Group, and provide a feedback channel. Follow the current Play Console instructions and resolve app setup or publishing issues before sharing the test link.
Read the full guide: How to Create a Closed Testing Track in Google Play Console →Plan recruitment and communicate the testing expectations clearly.
Recruit people who can access the test and are willing to participate throughout the testing period. You can use personal or professional contacts, relevant developer communities, and appropriate tester networks. Inviting a few more than the minimum can provide a practical buffer against opt-outs. However, only eligible testers who remain opted in count toward the continuous requirement.
Read the full guide: How to Find Testers for Google Play Closed Testing →Choose and manage the access method for your closed-testing audience.
Play Console allows closed-test access to be managed using email lists or Google Groups. For email-based testing, select the relevant tester list. For Google Groups, testers generally need to join the specified group before opting in. Keep the access list accurate and ensure your instructions match the method configured in Play Console.
Read the full guide: How to Add Testers in Google Play Console →Know the difference between an invitation, an opt-in, and an installation.
Sending a test link or adding an email address does not by itself establish that a tester has opted in. Each tester needs to complete the opt-in process for the applicable test. For a closed test using a Google Group, the tester must first join the group. Share the correct opt-in and installation instructions and verify that testers can access the release.
Read the full guide: How to Join a Google Play Closed Test →Plan the testing period and understand what happens if a tester opts out.
For eligible accounts, at least 12 testers must remain opted in continuously for the required 14 days before applying for production access. If a tester opts out and later opts in again, the earlier period does not combine with the new period to make 14 consecutive days. Track opt-in status and do not treat invitations or downloads as substitutes for the actual requirement.
Read the full guide: What Is the 14-Day Closed Testing Requirement? →Avoid preventable problems with access, releases, and tester counts.
Common issues include sharing the wrong link, forgetting the Google Group membership step, assuming an invitation means opt-in, losing testers during the required period, and leaving app setup or release problems unresolved. Test links may take several hours to become available after the first release or certain changes. Check Play Console status and the official instructions before changing your campaign.
Read the full guide: Google Play Closed Testing: Complete Guide →Build a meaningful testing process that helps improve the app.
A useful closed test is more than a headcount. Give testers clear tasks, ask them to explore relevant features, and provide a simple channel for reporting bugs and usability problems. Record the feedback you receive and the changes you make. Google asks about tester engagement and feedback collection when you apply for production access. Public reviews are not available for test versions, so use an appropriate private feedback channel.
Prepare for the application and the questions in Play Console.
Once the applicable testing criteria are met, open the Play Console Dashboard and select Apply for production. Google asks about the closed test, your app or game, and production readiness. Be prepared to explain how you recruited testers, how they engaged with the app, what feedback you received, what your app does, and what you changed based on testing.
Read the full guide: How to Apply for Google Play Production Access →Review functionality, policy compliance, privacy, and reviewer access.
Before applying, verify that core features work, crashes and major bugs have been addressed, app content and monetisation comply with Google Play policies, and the store listing and target audience are accurate. If your app requires login, provide working review credentials when requested in Play Console. Keep evidence of feedback and improvements so you can explain why the app is ready.
Read the full guide: Google Play Testing Requirements for Android Developers →Understand possible next steps and how to improve a future application.
An application may require more testing, including when the required number of testers is not continuously opted in or engagement is insufficient. Read the outcome and instructions in Play Console, address the issues, continue testing where needed, and document improvements before applying again. Never assume that reaching day 14 guarantees approval.
Understand what changes after the production track becomes available.
Production access allows you to proceed with a production release, subject to the applicable Play Console publishing and policy requirements. Review the production track, confirm the release configuration, and follow Google's publishing workflow. Approval for production access does not remove the obligation to comply with Google Play policies or pass applicable app reviews.
Read the full guide: What Happens After 14 Days of Closed Testing? →Get quick answers about timing, tester status, links, and approval.
Concise answers to the questions that come up most often, each one linked to the detailed guide or the official documentation behind it.
Get support with your closed-testing campaign, tester coordination, and the steps involved in preparing your app for production access. Review our service details and choose the support that fits your needs.
READ THE FULL GUIDES
Browse all guides →HOW IT WORKS
Built for first-time publishers passing Google Play's 12-tester closed testing requirement. If you get stuck anywhere, support answers on WhatsApp in minutes.
Check out in two minutes with just your email. We send your tester list right away; paste it into Play Console and share your test link with us.
YOUR PART: ~7 MINUTES
12+ verified testers install your app on real Android devices and use it every day, exactly the 12 testers for 14 days Google checks for. You watch each tester and each day live from your dashboard.
YOUR PART: NOTHING
Request production access and answer Google's short questionnaire. We hand you proven answers, and if Google pushes back, we retest free.
YOUR PART: ONE FORM
Testing starts in 4-6 hours · See the full process, step by step →
TESTING REPORTS
Every order runs the same five stages, and you can watch each one land in your dashboard. When the 14 days are done, the written report is waiting there to download.
We invite 12+ verified testers to your closed track and they opt in with their own Play accounts — you never chase a single one.
HOUR 0–6The counter starts the moment the last tester is in. The streak cannot skip a day, and that is exactly the part we own for you.
DAY 1Every tester installs and opens your app each day. Their notes, crashes and UI issues reach your dashboard as they happen.
DAYS 1–14We hand you the production questionnaire answers and walk you through the submit, so nothing is guessed or left blank.
DAY 14Production access granted — and your written testing report is ready to download from the dashboard.
DAY 15THE DELIVERABLE
Not an email you lose in a spam folder. Every order ends with a written report you can open, keep and hand to your team.
COMPARE
Two of them put your 14-day streak, and the $25 you paid Google, at risk. If you're comparing Android app testing services, here is the honest picture.
Ask friends, post in forums, chase people to keep the streak alive for two weeks.
Automated bot farms selling "testers" that Google's Play Protect detects quickly.
Real people on real devices, tracked daily for 14 days, with a written report at the end.
REVIEWS
Every review below is from a real order — the developer, the app they shipped, and what the 14 days actually felt like.
Breakdown of the 2 reviews published below
112+ COUNTRIES · 99.9% APPROVED
Closed Testing Done umar faruk
AgroCuentas Global
Verified client · United State
and also can upload client logo or by url will show mini size that suitable. and also can select users list from website register client if i select registred users then autu will match their profile name and logo app url. is it possible?
SHOWING 2 OF 2 PUBLISHED REVIEWS
ABOUT THE DEVELOPER
One developer builds and runs every closed test you buy — no agency, no account managers, no handoffs. You message him directly.
I build the tools behind this site — the dashboard, the payment flows and the app that drives it. Day to day I work in Flutter for Android and iOS, with Laravel and Firebase underneath, and I publish my own apps on Google Play.
This service started as a fix for my own problem: Google Play wanted 12 testers for 14 consecutive days, and chasing friends through the whole run was never going to work. So I built a system for it instead — and now it runs for other developers.
Fiverr
Upwork
Kwork
See the full profile — selected work, writing and every marketplace
LATEST GUIDES
Practical Google Play testing guides from TesterPilot. Everything we know about passing the 12-tester requirement, written down.
Google requires personal-account apps to run a closed test with at least 12 opted-in testers for 14 consecutive days before the production track unlocks. It is a per-app gate, and the days only count while at least 12 testers stay opted in.
Yes. Every tester is a real person on a real Android device, in their own country, using their own Play Store account. No emulators, no bots, no automation — Google checks for exactly that before it grants production access.
No. Google only counts how many testers stay opted in and how many consecutive days the test runs. The countries of the testers do not matter for the requirement. Most of our testers are in the US, UK, Canada and Europe, and they install the app with their own Google account.
Twelve is the legal minimum — we assign a small buffer on top of it. If one tester has a Play Store hiccup on day 9, the streak still holds while we replace them, because 12 testers remain opted in at all times.
No. Using real people to test your app is exactly what Google wants. Google does not prohibit using a testing service — every tester is a real human with a real device who opts in voluntarily, exactly like a friend you asked to test.
Yes. Each app runs its own 14-day test with its own testers and its own dashboard, so a second app never resets the first one. Message us for multi-app pricing.
Verified testers for 14 consecutive days, a live tracking dashboard you can refresh any time, daily install and usage proof, a written testing report at the end, and a money-back guarantee if Google still does not approve.
You paste the tester emails we send you into the closed-track tester list in Play Console, then share the opt-in link with us. It takes about 7 minutes, and the setup guide walks you through each screen.
Never. We only need the closed-track opt-in link plus the tester emails pasted in. Nobody on our side ever asks for your Google password, your 2FA code or your Play Console login — anyone who does is not us.
Internal testing is limited to 100 testers and does not count toward the 12-tester requirement. Only closed testing (or open testing) days count toward the 14-day streak, which is the track we run.
Three things: your app's package name, the closed-testing opt-in link from Play Console, and the tester emails pasted into the track. If you already have a draft order, everything is collected in the dashboard in one sitting.
Yes. If a closed test was rejected or has stalled, we take it over, run the full 14 days again with fresh testers and get you back to the production application. You do not need to start a new app listing.
The production track unlocks. You apply, we hand you the production questionnaire answers, and Google reviews the app. Most approvals land within a few days after the test completes.
Testing usually starts 4-6 hours after your order. You get your tester list right after checkout, and the 14-day clock starts the moment the last tester is opted in.
Cards and wallets through Stripe (Visa, Mastercard, Amex, Apple Pay), plus manual rails: USDT crypto, bKash, Rocket, Nagad, bank transfer, Fiverr, Upwork and Western Union. Card payments activate automatically; manual rails are confirmed by our team.
You choose: a free retest (we run the full 14 days again at no cost) or a full refund. No questions asked, and no arguing about whose fault it was.
The developer who runs the test — not a call centre and not a chatbot. Answers land by WhatsApp or email within 2-4 hours, and everything about your order also lives in your dashboard.
Nothing. Testers install and open the app every day, and you can watch each day land in the dashboard. If a tester stalls, we replace them before it can touch your streak.
CONTACT
The developer who runs your closed test answers this inbox himself — usually within 5 minutes, any day. Ask about pricing, Play Console setup, or a test that stalled on day 6.
Straight to the inbox above — nothing is outsourced.
Your 12 testers start the day you order.
From $14.99 · Starts in 4-6 hours · Free retest or full refund if Google does not approve
