Get 12 Google Play testers for your 14-day closed test.
Guaranteed first-try approval or your money back and a free second sprint!.
View Fiverr ProfileWhat is the Google Play 12-tester requirement?
If you created a personal Google Play developer account after 13 November 2023, you have to run a closed test before you can apply for production access. Here is the rule as Google publishes it.
- 12 testers means 12 users opted in to your closed test.
- When you apply, at least 12 of them must have been continuously opted in for the last 14 days.
- Google originally required 20 testers (announced November 2023) and lowered it to 12 starting December 2024; the two-week period did not change.
- Meeting this makes you eligible to apply. It does not guarantee production access: Google separately reviews engagement, feedback and app readiness.
Source: Google Play Help: App testing requirements for new personal developer accounts. Last reviewed: .
How to get 12 testers for Google Play: your three options
Recruit them yourself
14 days of admin- One dropout can leave you under 12 testers
- You chase a dozen strangers, every day
- No proof anyone actually opened it
- No guarantee of approval
Two weeks of efforts for nothing
Cheap testing services
Risks your console- Emulators and farm accounts get flagged
- One opt-in, then they never open it again
- Your developer account takes the hit
- No guarantee of approval
Account suspension risk
Teekam's Testers
What we do- 12+ real testers on their own phones
- Genuine daily use, all 14 days
- Refund + free re-sprint if our testing is the cause
Starting at just $25
How our Google Play testers run your 14-day closed test
Setup & Tester Enrollment
Invite our testers (or add our Google Group) and send us the opt-in links. Within a few hours, 12+ real Android users install your app and stay opted in, with daily sessions so Google sees continuous, genuine activity.
Live within hoursTesting QA Report
Around week one you get a written QA report - real bugs, device details, and clear repro steps - so you can polish the app before you apply.
Shared after week 1Production Guide
On Day 14 you receive tailored Apply for Production questionnaire answers. Follow the guide, paste the answers, and submit with first-try confidence.
Ready on Day 14Production Access
Once Google approves, you're cleared for production - congratulations. Your app can go live on the Play Store, and we stay available if you need anything after approval.
You're approved
What happens during the 14 days of testing
Your 14-day streak
UnbrokenOne square per day. A square only fills when every tester in your cohort has actually opened the app.
No reminders to send, no spreadsheet to keep, no days to count.
You ship the app. We keep the streak.
- 01
They open it. Every single day.
Each tester runs your app on their own phone the way a real user would - onboarding, the core flows, the screens you're least sure about. Installed and opted in from day one to day fourteen.
- 02
They write down what broke.
Crashes, dead ends, slow screens, confusing copy - all logged with the device model and the exact steps to reproduce it. Those notes are what your QA report is built from.
- 03
We're counting so you don't have to.
Every opt-in and every active day is tracked on our side. The moment a tester goes quiet, a backup from the same pool takes their place - before your count is ever at risk.
Fourteen days of testing, written down: your QA report
QA Feedback Report
14-day closed test · 12 testers
01
Ranked, not just listed
Every finding carries a severity and a priority, so you know what has to be fixed before launch and what can wait.
02
Tied to a real device
Each issue names the phone and Android version it appeared on, along with the steps to reproduce it yourself.
03
Yours as a PDF
The full write-up lands at the end of the sprint. Keep it, share it, hand it straight to whoever fixes the bugs.
Every sprint includes one. Longer plans go deeper.
- A short read on how the 14 days went
- Findings per tester, with device and Android version
- A severity and priority call on every issue
- Steps to reproduce each bug we hit
- Screenshots, plus the UX changes worth making
What production access looks like once you apply
Google Play
noreply@google.com
460+
Apps approved
100%
Success rate
0
Policy strikes
3+
Years proven
Fiverr reviewsWhat Fiverr buyers say after successful approvals.
5.0
Fiverr SellerTop rated | Since 2019
460+ orders completed
"Teekam and his team have done an outstanding job testing my app over the past 14 days to prepare it for Google Play Production. What stood out most was his communication throughout the process. He kept me updated with regular reports and were always quick to respond to questions or clarifications, making the entire experience smooth and collaborative."
deepinkcode
Verified order · Canada
"Teekam did an awesome job on testing my game over the past 14 days for the google play store. Communication was great and I was regularly updated on the progress. Would recommend to anyone that needs testing for google play."
mattgleason90
Verified order · United States
"I would definitely use this gig in the future! The seller was polite, was willing to go above and beyond, delivered on time (even early), had a deep understanding and level of cooperation, proactive communication and quick responsiveness. Thank you!"
mccroryj
Verified order · United States
r/testimonialsWhat Reddit developers say.
r/testimonials
u/AppBernard
Working With Teekam Suthar
Hey, I just wanted to make a post to thank Teekam Suthar and his team for helping me test my app Hughie and release to production. He was very professional throughout the entire process and I loved how he gave me a document with detailed feedback on current issues found during testing and even suggestions on how to fix them. He not only helped me meet Google's testing requirements but also made me more confident my app would work well in production. I would recommend anyone considering working with Teekam to give him a shot, I am sure you will be happy!
Read on Reddit →
r/testimonials
u/Sygall_
If you struggle to release your app on the Playstore, u/teekamsuthar is your man.
If you need someone to test your android app in order to release it on the Playstore, u/teekamsuthar is definitely the man you need. For $25, you'll get your 12 super-reliable testers for the required 14 days so you'll be able to request a production access from Google. That's it. No need to force your unreliable cousin or brother-in-law to keep testing your app every day for two weeks anymore. Just go PM this guy, sit back, relax and enjoy getting things done with 0 effort.
Read on Reddit →
r/testimonials
u/Hippoterus
Testing Review
I reached out to Teekam (u/teekamsuthar), after some time cause I wasn't sure about the offer he had made. It turned out to be one of the simplest and most efficient ways to pass the closed testing phase inside Google Play Console. I am very grateful for the opportunity and the work that went into the testing phase. Thank you and your team. Very good service, clear communication.
Read on Reddit →
See how it played out, and read the details
Real closed tests we ran
Sea Guardian: Tanker Escort
An arcade game on a new personal account: 16 real testers, a written QA report on day 6, and the production-access outcome.
Read the case study →
UGC Hub
A creator platform's 14-day closed test, a 9-finding QA report (5 issues and 4 enhancements) and the approval outcome.
Read the case study →
MyLifelens
A first app through closed testing, with a paywall bug caught before launch.
Read the case study →
Guides worth reading first
Teekam Suthar
Android developer · Founder of Teekam's Testers
I'm an Android and Flutter developer with 5+ years of freelance work, and my own app Mutify has 1M+ downloads on Google Play. I started Teekam's Testers in 2023, when Google began requiring closed testing for new personal accounts. Every test is run by my team of real testers on their own Android phones.
More about me →Start your closed test today. Pay later.
How it works
You share your app link
Takes two minutes.
We enroll our 12+ testers
All our testers are real and join within a few hours.
You pay only after testing is commenced
Pay only after you have watched us work. Cancel before enrollment and you owe nothing.
What's included
- 12+ real Android testers
- Comprehensive testing QA report
- Tailored production application answers
- Support until you get production access
What you pay
- Today
- Free
- After testers enrollment
- Starting $25
One payment, no subscription. Cancel before enrollment and pay nothing.
460+ apps approved · 100% first-try success rate · Same-day setup
Our "First-Try" Approval Guarantee
If Google rejects your production access because of our testing metrics, you get a full refund and a second 14-day sprint at no cost.
Full money back
Every dollar refunded, no conditions and no argument.
Free 14-day re-sprint
We run the entire sprint again, start to finish, at no charge.
Zero policy violations
Nothing in our process puts your developer account at risk.
Google Play closed testing: your questions answered
Real questions developers ask about the 12-tester requirement, answered plainly.
Most asked
Does hiring testers violate Google Play Policy?
No. It is completely within Google's policies to use third-party networks to fulfill your testing requirements. This is officially documented in the Google Play Developer Community Guide, which explicitly states developers can utilize external testing groups.
Read official documentation →
Does the 12-tester rule apply to my developer account?
It applies to personal developer accounts created after 13 November 2023. Google's requirement page doesn't cover older personal accounts or organization accounts. If you're not sure, open Play Console: on an account the rule covers, Production stays disabled until you meet the testing requirement.
Can I get testers for free?
Yes. Friends, family, your own audience, topic communities and developer tester-exchange groups are all free. The usual catch is reliability: unpaid testers often opt in once and drift away, so recruit above 12. A managed service like ours costs money but removes the recruiting and the daily chasing.
Do your testers use real Android devices?
Yes. Our testers use their own real Android phones, not emulators or farm accounts. Emulators and scripted accounts look like non-genuine activity and put your developer account at risk.
What happens if the tester count drops below 12?
If a tester opts out before 14 days they stop counting, and if they opt back in the 14 days must be consecutive again. We enroll more than 12 and track opt-ins, with backups ready from the same pool, so one dropout doesn't put you under the minimum.
Do I need new testers for every app?
Google doesn't publish a rule requiring a different group per app. What matters is that at least 12 testers are continuously opted in to that app's closed test for the last 14 days, and that the testing reflects real use.
Does 12 testers guarantee production access?
No. Meeting 12 testers for 14 days makes you eligible to apply, and Google makes the final decision. What we guarantee is our side: if Google rejects you because of our testing metrics, you get a full refund and a free second 14-day sprint.
What happens if a tester uninstalls the app?
They don't. We run a strictly audited, paid cohort of real users. We monitor daily opt-in status to guarantee your 14-day continuous timer never resets.
What types of apps are eligible for testing?
We provide testers for all apps and games submitted to the Google Play Console, as long as they are functional and ready in their initial version.
What sets your service apart from others?
We are a team of mobile developers who have shipped hundreds of apps. We don't deliver bare minimum to fulfill the requirements, we properly test your app and provide documented actionable feedback for your app so you can polish and release new updates before going for production
How many testers do I need for Google Play closed testing?
At least 12 testers, continuously opted in for at least the last 14 days when you apply for production access. Google's requirement page covers new personal developer accounts created after 13 November 2023.
Did Google change the requirement from 20 testers to 12?
Yes. Google announced 20 testers in November 2023, then lowered the minimum to 12 starting December 2024. The two-week testing period did not change, so today's rule is 12 testers for at least 14 days of continuous opt-in. Older tutorials that say 20 predate the change.
How long does the 14-day closed test take?
At least 14 days. Google requires testers to be continuously opted in for at least the last 14 days before you apply for production access. After day 14 you can apply, and Google then reviews your testing, feedback and app readiness.
Do testers need to use the app every day?
Google's published requirement is about continuous opt-in, but Google also reviews engagement and feedback when you apply. Our testers open and use your app across the 14 days and log what they find, so you have real material for the questionnaire.
Can my testers be in different countries?
Generally yes, but each tester's country needs to be included in your closed track's countries and regions, otherwise they can't get the app from that track.
Why does Play Console show fewer testers than I invited?
Play Console counts opted-in testers, not invited ones. Testers who haven't opened the link and accepted, accepted with a different Google Account, haven't joined your Google Group, or are opted in to your internal test won't be counted.
Who writes the production access questionnaire answers?
We've been doing this since 2023. We'll write the answers for you, tailored to your app, so your answers are specific and honest instead of vague.
How does the Refund + Free Retest guarantee work?
If your app is rejected specifically because Google flags the closed testing phase as having 'insufficient engagement', we will instantly refund your payment. On top of that, we will place your app into our next testing cohort and run a new 14-day sprint for free.
How do I prepare my app for testing?
You just need to start the closed testing track and upload the initial build in the Google Play Console. We will provide detailed step-by-step instructions and screenshots to help you set this up and invite our testers.