REAL TESTERS · REAL DEVICES
Real people test your Android app on real devices. We handle the process, from closed testing to Play Store readiness, so you get a clear, prioritized report and know exactly what to fix before launch.
Real testing. Real insights. Play Store ready.
Our testers use real devices in real conditions to find issues automated tools can't. We deliver clear insights and actionable reports so your app is stable, compliant, and ready to grow on Google Play.
Why AppsTestLab
AppsTestLab combines hands-on app testing with deep Google Play knowledge, so you get more than a report, you get a path forward.
Every test is performed by real people on real Android devices, not simulators. You get feedback that reflects how actual users experience your app.
We specialize in the Google Play ecosystem: closed testing, Play Console, production access, and the publishing workflows that trip up developers.
Testing produces clear, prioritized findings with practical next steps, not vague summaries. You know exactly what to fix and why.
One WhatsApp message gets everything started. No dashboards to learn, no ticketing systems. You talk directly to the team handling your test.
5,000+
Apps Tested
Apps that have gone through our testing service/process
99%
Historical Approval Rate
Approximately 99% of apps we've tested have gone on to achieve approval. Based on our completed testing projects.
100%
Money-Back Guarantee
On eligible app testing orders
How to read these numbers: apps counted here are apps that have gone through our testing service. Google makes all final approval decisions, and these figures reflect AppsTestLab's historical service records.
What we do
End-to-end app testing for Android developers, from first install to Play Store readiness. Pick the chapter that fits where your app is today.
Browse all servicesGet your app tested on real Android devices before users find problems. Testers install, use, and report issues on their own hardware.
Get the testing process organized for Google Play requirements, from setting up tracks to meeting tester count thresholds.
Meet Google Play closed testing requirements with real testers participating over the required duration. We coordinate the process.
Find broken flows, crashes, and usability concerns before your users do. Testers use your app on their own devices and report what goes wrong.
How it works
A simple, direct process, from first message to shipped results.
01
Share your app details on WhatsApp: what it does, what you need tested, and any concerns you have.
02
We recommend the right number of testers and testing scope for your app and goals.
03
Our team coordinates testers on real devices. You get progress updates throughout.
04
A clear, prioritized report with practical next steps, not vague summaries.
The real cost of testing
The cheapest testing option is not always the lowest total cost. Developer time, coordination effort, and feedback quality all affect how much testing actually costs you.
Total cost = price + time + coordination + risk
Coordination overhead
Lowest upfront price
You recruit testers, track opt-ins, manage the schedule, and follow up on incomplete sessions.
AppsTestLab
One team coordinates the entire cycle. You send a link and wait for the report.
Tester recruitment
Lowest upfront price
Finding enough reliable testers who actually install, use, and provide useful feedback takes time.
AppsTestLab
Our tester pool is already built. Inactive testers are replaced automatically.
Play Console learning
Lowest upfront price
Closed testing tracks, opt-in requirements, production access rules. Each one has its own workflow.
AppsTestLab
We handle the process. You do not need to learn every Play Console detail.
Feedback quality
Lowest upfront price
Scattered notes, vague comments, and inconsistent formats that you have to interpret yourself.
AppsTestLab
Structured, prioritized reports with clear next steps. You know exactly what to fix.
Repeat testing
Lowest upfront price
If the first round does not go well, you restart the process from scratch.
AppsTestLab
Tester replacement and cycle management are part of the service.
Choose your starting point
Every package includes real testers on real devices. The difference is how many testers you get, how detailed the feedback is, and how much support you need.
Standard
Actionable feedback
Best for broader testing and actionable feedback
You need more than checkbox testing. You want real findings with practical next steps.
Basic
Requirement coverage
Best for meeting the testing requirement
Google Play requires 12 testers opted in for 14 days. You need the process handled without learning every Play Console detail.
Premium
Deeper coverage
Best for complex apps that need deeper coverage
Your app has multiple flows, edge cases, and device-specific behavior. You need thorough coverage.
Not sure which fits? Tell us about your app and we will help you choose.
Why AppsTestLab
There are three common ways to approach Android app testing. Here is how each one compares on the dimensions that matter most.
Handle it yourself
Testing coordination
You recruit testers, manage opt-ins, and track the testing period yourself.
Real-device testing
You test on whichever devices you personally own.
Structured reporting
You compile findings from scattered tester feedback into your own reports.
Google Play expertise
You learn Play Console workflows, policies, and testing tracks as you go.
Tester management
You handle recruitment, follow-up, and replacement of inactive testers.
Your time
Significant time spent coordinating, learning, and managing the process.
Hire freelancers
Testing coordination
Depends on the individual provider and scope.
Real-device testing
Varies. Some providers use emulators or limited device pools.
Structured reporting
Varies. Some provide summaries, some provide raw notes.
Google Play expertise
Some specialists cover parts of the process.
Tester management
Depends on the provider.
Your time
You manage each provider relationship separately.
AppsTestLab
Testing coordination
Handled end-to-end. One team coordinates testers, tracks opt-ins, and manages the full cycle.
Real-device testing
Real people on real Android devices across multiple manufacturers and OS versions.
Structured reporting
Clear, prioritized reports with actionable next steps. You know exactly what to fix.
Google Play expertise
Deep expertise across closed testing, production access, store listings, and Play Console configuration.
Tester management
Inactive testers are replaced automatically. The testing cycle stays on track.
Your time
One WhatsApp conversation. One team handles coordination, testing, and reporting.
Public customer feedback
Reviews from customers who purchased our testing services through the public Fiverr profile. Every review below is hosted on Fiverr and can be checked there directly.
Customer wording kept as published · linked to the original on Fiverr
Rating shown on our public Fiverr profile
4.9
74 public reviews
As rated by buyers
Seller communication
4.9
Quality of delivery
4.9
Value of delivery
4.9
Verified on Fiverr
Fiverr · Gaurav Kumar · @gaurav_iop“Fantastic experience! This freelancer tested our Google Play app and did an absolute flawless job. Communication was spot on, the turnaround time was lightning fast, and everything went incredibly smoothly. Highly recommended, and I’ll definitely be back for future projects!”
@jiri_lebeda · Czechia
May 2026
“Failed to get it approved several times on my own. Got it my first time with his help!”
@camrenbt · United States
December 2025
“Again, third app in a row got approved with his help! Thanks a lot”
@kotysoft · Ireland
April 2026
“Gaurav carried out the testing professionally and very quickly. After his testing, I received approval from Google to publish the app. Previously, I had two rejections, but thanks to Gaurav’s work, the publication issue was finally resolved. He also provided clear answers to every question in the Google Play publication survey.”
@vic_pozdnyakov · Kazakhstan
December 2025
“App reached production, testing as promised”
@seryusjj · Switzerland
April 2026
“good communication, good support, helped when I had a question.”
@vilaproperties · United Arab Emirates
May 2026
Nine selected reviews are shown on the Reviews page, with filters for the kind of feedback you care about.
View all reviewsPublic credibility
Since June 2023
Tutorials, explanations, and practical solutions for Android testing, Play Console, and app publishing problems, published from the public channel.
AppsTestLab · YouTube
Educational content for developers and app publishers
Tutorials, explanations, and practical solutions for Android testing, Google Play Console, and app publishing.
Public channel · since June 2023
Visit our YouTube channel@appstestlabb
Google Play • Closed Testing
A practical walkthrough of Google's closed-testing process, from finding the right testers to completing the testing period and requesting production access.
Index
12 chaptersNeed help with testing?
AppsTestLab coordinates testers so you can focus on your app.
Start on WhatsAppIf you created a personal Google Play developer account after November 13, 2023, you must run a closed test with at least 12 testers for 14 continuous days before you can apply for production access. This is the requirement that affects most new individual developers today.
Organization accounts (registered as a business or institution) are not covered by this rule. Accounts that already had production access before November 13, 2023 are also not affected. The status shown in your Play Console Dashboard is the final word for your account.
| Account type | Created before Nov 13, 2023 | Created after Nov 13, 2023 |
|---|---|---|
| Personal | No closed test required | 12 testers, 14 days required |
| Organization | No closed test required | Not covered by this requirement |
What the rule means
What this does NOT mean
Google Play Console offers four release tracks. Understanding the differences helps you figure out why closed testing is the track that matters for the 12-tester requirement.
| Track | Who can join | Visibility | Counts toward production |
|---|---|---|---|
| Internal testing | Up to 100 invited testers | Private | No |
| Closed testing | Testers you add (email/Group) | Private | Yes |
| Open testing | Anyone who opts in | Public on Play Store | No |
| Production | Everyone | Public on Play Store | N/A |
Closed testing lets you share a pre-release build with a controlled group. Testers install from Google Play, use it on real devices, and provide private feedback that never appears on the public store and never affects your app's rating. Unlike internal testing, it requires your app setup to be complete and is the track Google counts for production access.
Why closed testing matters
Setting up a closed test in Play Console is straightforward, but your app needs to be ready before you start. Here is the workflow.
Open Play Console and select your app
Navigate to Testing, then Closed testing.
Complete app setup if needed
Your app needs a store listing, content rating, privacy policy, and a signed build (AAB or APK).
Create or open your closed test
Create a new closed test or select an existing one. Upload your release.
Set release countries
Choose the countries where testers can access the test. Testers must be in one of these countries.
Publish the test
Publish the release to the closed testing track. It can take a few hours for the test link to become available.
Prepare before creating the test
Play Console gives you two ways to add testers: an email list or a Google Group. Both work, but each has tradeoffs.
Email list: Add tester email addresses directly in Play Console. Straightforward, but you manage each email individually.
Google Group: Create a group, add members, and link the group to your closed test. Play Console syncs membership automatically. Easier to manage at scale.
Who can be a tester? Anyone with a Google Account. They do not need to be developers or technical. They just need an Android device and a Google Account that matches the email you listed.
Start with more than 12 testers
Adding testers to your list is only the first step. Each tester must complete an opt-in process before they appear as active in Play Console.
Share the opt-in link
Send the testing URL to your testers via email, messaging, or other channel.
Tester opens the link on their Android device
The link must be opened on the device where they will install the app.
Tester signs in with their Google Account
This must match the email you listed in Play Console.
Tester opts in and installs
They accept the invitation and install the test build from Google Play.
Account matching is critical
Common problems: tester used a wrong Google Account, link not working, app not visible, or tester cannot install. Usually the fix is confirming the tester used the correct account and completed the full opt-in flow.
At least 12 testers must remain opted in continuously for 14 consecutive days. The period is counted from when testers actually opt in, not from when you add their email addresses.
Continuous opt-in
Here is how the timeline works in practice: you add 15 testers on Day 1. Eight opt in on Day 2. Five more on Day 3, bringing you to 13. Two more on Day 4, bringing you to 15. Now that you have at least 12, the 14-day period begins. Your earliest eligible date is Day 18 (Day 4 plus 14 days).
If on Day 14 a tester opts out and you drop to 11, the streak is broken. You need a replacement and must restart the 14-day count.
Myth: testers must open the app every day
This is why starting with exactly 12 testers is risky. If even one person drops out, you fall below the minimum. Starting with 15 to 20 gives you a safety margin.
During the 14-day period, your job is not just to wait. The goal is genuine testing, not just filling a time requirement.
Need the testing process coordinated for you?
AppsTestLab handles tester coordination so you can focus on your app. We help you run a genuine test that supports a strong production access application.
Start on WhatsAppThere is a difference between a tester who is "opted in" and a tester who is "actually engaged." Opting in means they completed the flow. Engaging means they are actively using the app and providing useful feedback.
Google has indicated that tester engagement can affect the production-access review. Having 12 people who opt in but never open the app is less valuable than having 12 people who genuinely use it.
What testers should do:
Guide your testers
You added 12 testers but Play Console shows 0 opted-in testers. This is one of the most common problems developers encounter. Here are the likely causes.
What to check:
Email list vs. opt-in status
Completing the 14-day testing period does not mean Google automatically approves your app. The testing period makes you eligible to apply. Production access requires a separate application.
Play Console notifies you
You may see a notification or dashboard banner indicating you are eligible.
Navigate to the production access request
This is usually accessible from your dashboard or the Policy & programs section.
Answer questions about your test
Covering tester recruitment, engagement, and feedback collection.
Google reviews your submission
The review typically takes 7 days or less, though it can sometimes take longer.
You receive a decision
If approved, your app can be published to production. If not, Google provides feedback.
Application is a separate step
Google asks three groups of questions. Answering them truthfully and specifically is the best strategy.
Group 1: About your closed test
Group 2: About your app or game
Group 3: About production readiness
Answer honestly and specifically
Want the testing process handled instead?
AppsTestLab manages the entire closed testing process, from tester coordination to feedback collection. We help you run a genuine test that supports a strong production access application.
Start on WhatsAppEven after completing the minimum testing period, Google can require additional testing. This does not mean the process failed. It means Google identified areas that need more work.
Common reasons for rejection:
What to do if rejected:
Read Google's response carefully
Google typically explains why the application was not approved.
Identify the specific weakness
Was it low engagement? Weak feedback? App quality issues?
Continue testing with genuine engagement
Focus on getting testers to actually use the app and provide feedback.
Improve the app based on feedback
Fix bugs, address usability issues, make real changes.
Reapply when genuinely ready
Only submit a new application when you have addressed the issues Google identified.
Genuine testing matters more than time
Showing chapter 01: Do I need 12 testers?
FAQ
Every developer preparing an app for Google Play asks the same things: how many testers, how long it takes, and what happens if the app gets rejected.
Can't find your answer?
Tell us what you're building and we'll help you figure out the right testing approach.
Chat on WhatsAppAppsTestLab is an independent Android app testing service. We coordinate real people to test your app on real Android devices, then collect and structure their feedback so you know what to fix before launch. We are not affiliated with Google — Google makes all final decisions about your app and account.Explore our testing services →
We test Android applications — new apps preparing for their first release as well as existing apps shipping updates or bug fixes. Testers install your app on their own physical devices and use it the way real users would, then report what they find. If you're unsure whether your app fits, message us on WhatsApp and we'll confirm before you commit.
Contact us on WhatsApp with a short description of your app and what you're trying to accomplish. We'll confirm what applies to your situation, recommend a package, and set up the testing track. After you've chosen a package, we confirm the details on WhatsApp and testing starts shortly after.
For our standard Google Play testing service you need: 1) your app available on the appropriate Google Play testing track, 2) our tester group added to that track — appstestlab@googlegroups.com, 3) the Google Play testing / opt-in link, 4) test credentials if your app requires login, and 5) optionally, testing instructions or specific flows you want us to focus on. You do not need to send us an APK or AAB — our testers access your app through Google Play.Developer account setup →
No. For our standard Google Play testing service, you do not need to send us the APK or AAB directly. Add appstestlab@googlegroups.com to the appropriate Google Play testing track and send us the Google Play testing / opt-in link.
Open your Google Play Console and go to your testing track, add this Google Group as a tester — appstestlab@googlegroups.com — save or publish the configuration, copy your Google Play testing link, and send the link to us on WhatsApp. Our testers then access and install your app through Google Play. If your app requires login, share the test credentials on WhatsApp too — never post credentials publicly.
You tell us about your app on WhatsApp, we agree on a package and a testing method, then we coordinate testers to install and use your app on real Android devices over a 16-day cycle. Testers report bugs and observations, we collect and structure the feedback, and you receive a report with findings and actionable next steps.See our testing process →
Yes. We coordinate the closed testing process end to end: we recruit and confirm testers, make sure they opt in and stay opted in, and track that your account keeps enough testers during the requirement window. We're an independent service — Google makes all final decisions about your account and production access.Google Play closed testing →
Google's current requirement for eligible personal developer accounts created after November 13, 2023 is a closed test with at least 12 testers opted in for at least 14 continuous days before you can apply for production access. Requirements differ by account type and can change over time, so we confirm what applies to your account before you commit.Google Play testing service →
Google requires at least 12 testers to be opted in for at least 14 continuous days before production access is requested for eligible accounts. Our standard testing cycle runs 16 days, so the continuous 14-day window is comfortably covered while testers put real usage time into your app. Google makes the final call on your application.
No service can guarantee Google approval — Google makes every final decision. What we guarantee is our own work: we historically helped roughly 99% of the apps we tested reach launch, and if your app is not approved after our eligible testing, you get a full refund under our money-back guarantee.Our guarantee →
Real Android devices — never emulators. Our tester pool covers phones and tablets across different manufacturers, Android versions, and screen sizes, so your app is exercised on hardware that matches what real users hold. We won't claim a device mix we can't deliver; on WhatsApp we'll tell you the devices available for your app before testing starts.
Our standard cycle runs 16 days — long enough for testers to genuinely use the app, and long enough to cover the 14 continuous days Google asks for in eligible closed tests. Initial feedback usually arrives within the first few days; the full report arrives when the cycle completes.
Testing is a flat fee per app: Basic (12 testers) is $10, Standard (15 testers) is $15, and Premium (20 testers) is $20. Every package covers a 16-day testing cycle with real testers on real devices. There are no hidden fees — the price is agreed on WhatsApp before testing starts.
If your app is not approved after our testing, you get a full refund of your eligible testing order — no questions asked. The guarantee covers eligible app testing orders; store listing, ASO, design, and other non-testing services are not covered. Ask us on WhatsApp if you're unsure whether your order qualifies.Full guarantee details →
No. Google makes every final approval decision, and no service can guarantee it. Our guarantee is a promise about our own work: if your app is not approved after our eligible testing service, we refund that service. Combined with our historically strong approval rate, it's how we stand behind our testing.
Ready to test?
Tell us about your app and we'll confirm the right testing approach. One WhatsApp message to start, no complicated setup.
Guarantee applies to eligible app testing orders · Google makes the final approval decision
