Google Play closed testing service

Get 12 testers for 14 days — Google Play closed testing

From $16 for one app · $30 for two apps. Each run includes 14 real Android testers across a managed 16-day window with opt-ins, monitoring, and a closeout report.

Start from $16 See the process

14 testers included
Real Android devices
16-day managed window

Reviewed against Google Play guidance · Updated July 16, 2026

Illustration showing 12 Android testers and a continuous 14-day Google Play testing calendar — **12 testers**opted in across one continuous 14-day window

From $16one managed app run

14 testerstwo above Google's minimum

16 daystwo-day operational buffer

1 dashboardprogress and reporting visibility

Simple pricing

One app for $16. Two apps for $30.

Every credit covers one managed Android app testing run with 14 verified testers across 16 calendar days.

For one release

Basic

$16

1 credit for 1 app

1 credit - covers 1 app test run
14 verified testers
16 calendar days of testing

Buy Basic $16

Best value

Premium

$30

2 credits for 2 apps

2 credits - covers 2 app test runs (1 credit = 1 app)
14 verified testers
16 calendar days of testing

Buy Premium $30

The extra testers and days provide an operational buffer above Google's 12-testers-for-14-days minimum. Completing a test lets an eligible account apply; Google makes the final production-access decision.

What you are buying

A managed testing run—not a list of disposable accounts.

The minimum is simple on paper. The operational work is getting every tester through the correct Play Console flow, keeping a safe opted-in count, collecting useful feedback, and documenting what changed before you request production access.

12+ verified testers

Real Android users join through your official Google Play closed-testing opt-in path.

Full 14-day coverage

The opted-in group is coordinated across the complete continuous testing window.

Buffer and monitoring

Participation is monitored so you can react before the tester count becomes a launch risk.

Testing closeout

You receive participation and feedback notes to prepare specific production-access answers.

Illustration of a Google Play closed-testing dashboard on an Android phone

The requirement

What Google officially requires

Google states that affected new personal developer accounts must run a closed test with at least 12 testers who have been opted in for the last 14 days continuously before applying for production access.

Applies to affected personal developer accounts created after November 13, 2023
Requires at least 12 testers opted in to a closed test
The testers must cover the last 14 days continuously when you apply
Completing the requirement allows you to apply; Google still decides production access

Official Google requirement

Managed process

From your opt-in link to a production-access-ready testing record

Kickoff

Share your opt-in link and build details

Create your closed testing track in Play Console, upload the build, and send us the opt-in link. Most runs are assigned within about 24 hours.

Opt-in

12+ verified testers join your closed test

Each tester accepts the invite with a real Google account and installs your app on a physical Android device. Your Play Console tester count reaches 12 and the 14-day clock starts.

14 days

Continuous activity across the full window

Testers open and use your app across the window while we monitor participation. Buffer capacity helps reduce the risk of the opted-in count falling below 12.

Apply

Apply for production access with evidence

After day 14 you get a run report covering tester activity and feedback — concrete material for Google's production access questionnaire.

Illustration of tester participation tracking and a structured testing report — Track participation, feedback, and the testing window in one workflow.

Progress visibility

See where your testing run stands.

Your workspace brings the testing timeline, active assignments, progress updates, and reports together so you are not piecing status together from chat messages.

Testing status and 16-day timeline
Active tester assignment count
Progress updates and tester reports
One place for each app test run

Example testing workspaceActive

ANDROID CLOSED TEST

Release candidate

Day 8 of 16

8 days complete8 days remaining

Assigned testers14Active

Reports received9Updated today

Run statusOn trackWindow active

Latest updates

Testing is underwayUsage checks and feedback collection continue.

Today

All testers assigned14 participants joined the managed run.

Day 1

Illustrative preview based on the TestMyApps run workspace.

Why teams buy managed testing

Price, visibility, support, and honest scope

Clear pricing

$16 for one app or $30 for two — published on this page, no sales call required.

Run visibility

Timeline, assignments, progress updates, and reports in your TestMyApps workspace.

Support included

Email and WhatsApp if opt-ins, assignments, or reporting get blocked.

Honest scope

We coordinate closed testing. Google still decides production access.

Apps on Google Play

400+ apps supported through closed testing

A few recent Play Store launches below. Each link opens the live listing on Google Play.

400+Android apps supported through managed closed testing

Showing recent examples. TestMyApps has supported 400+ app testing runs across indie, agency, and first-time publisher launches.

Developer feedback

What developers say after a managed closed test

Real quotes from developers who ran managed testing runs. Production access still depends on Google's review of your app and answers.

“Got my Play Store approval in days. The testers were fast and professional.”

Rahul S

Android Developer

“Much easier than finding testers manually. Everything is managed in one place.”

Ankit Verma

Startup Founder

“Bug reports were clean and useful. Helped us fix issues quickly.”

Priya N

Product Manager

“The 14-day window finished without a single tester dropping out. Production access came through on the first application.”

Daniel K

Indie Developer

“We shipped two apps through their closed testing runs. The status updates made it easy to plan our launch dates.”

Meera T

Agency Lead

“Clear pricing, real devices, and testers who actually used the app daily. Exactly what Google wants to see.”

Josh M

Mobile Engineer

Common failure modes

Most 14-day delays come from coordination—not code

Invitations sent, but testers never complete the official opt-in

A different Google account is used for opt-in and Play Store installation

The count falls below 12 because there is no tester buffer

The app produces little useful feedback for the production-access questionnaire

Start your testing run

Bring your Play Console link and start closed testing

Choose a plan, share your closed-testing details, and keep your product team focused on fixes instead of recruitment and reminders.

See $16 and $30 plans

FAQ

FAQ before you buy a 12-tester run

Completing the closed-test requirement lets an affected account apply for production access. It does not guarantee approval of the app.

What exactly is the 12 testers for 14 days requirement?

Google requires newly created personal developer accounts to run a closed test with at least 12 testers who have been opted in for the last 14 days continuously before the account can apply for production access on Google Play.

How do I get 12 testers for 14 days quickly?

The fastest reliable route is a managed testing service. TestMyApps assigns 12+ verified Android testers within about 24 hours of receiving your closed testing opt-in link, and keeps them active for the full 14-day window.

What happens if a tester opts out during the 14 days?

If your opted-in count drops below 12, the continuous window can break and the clock may restart. TestMyApps monitors the count daily and keeps buffer testers ready so a dropout is replaced before it affects your timeline.

Do the testers need to use my app every day?

Google's written rule focuses on continuous opt-in, but reviewers also look at engagement when you apply for production access. TestMyApps testers open and use your app across the window so your application shows genuine activity.

Does internal testing count toward the 12 testers requirement?

No. Only the closed testing track counts. Internal testing is useful for early QA, and open testing only becomes available after production access.

When can I apply for production access?

Once Play Console shows at least 12 testers opted in for the last 14 continuous days, the Apply for production option appears on your dashboard. You then answer a questionnaire about your testing process before Google reviews the application.

Are these real people or bots?

TestMyApps uses real people testing on physical Android devices. We do not use bots, emulators, or duplicate accounts for managed closed-testing runs.

Verified references

Official sources and next reading

Google Play Console HelpTesting requirements helpApp testing requirements for new personal developer accounts

Google Play Console HelpClosed test setup helpSet up an open, closed, or internal test

Closed testing guideSetup, tracks, and troubleshooting for Google Play closed testing.

Timeline estimatorEstimate when your 14-day opt-in window completes.

Full pricing pageCompare credit packages for managed closed-testing runs.