The Complete Android Closed Testing Guide: From Securing 12 Testers to a 14-Day Finish

To successfully launch an Android app on Google Play, you must go through the Android Closed Testing phase. This complete guide covers every requirement, procedure, and success strategy for closed testing in detail.

What is Android Closed Testing?

Android Closed Testing is a test distribution system provided by Google Play Console. It restricts app access to a limited group of users, allowing you to verify the stability and functionality of your app on real devices before the production release.

The Importance of Closed Testing

For personal developer accounts created after November 13, 2023, Google Play requires Closed Testing before a production release (organization accounts are not subject to this). Through it, you can:

• Verify behavior on real devices: See how your app actually works on real devices rather than emulators
• Catch bugs early: Find and fix critical bugs before release
• Improve the user experience: Refine the app with feedback from real users
• Comply with store policies: Meet Google Play's quality standards

Essential Requirements for Android Closed Testing

To release to production on Google Play, you must meet the following conditions.

1. 12+ Testers (Critical)

This is the most demanding requirement. It's not simply about the number of people on your tester list — you need 12 or more testers who have opted in (accepted the invitation via your opt-in link). The number was 20 until December 2024; it is now 12.

> Important: Being on your tester list does not count. Testers count only after they opt in, and the opt-in link only works once the closed testing release is Published.

2. 14 Consecutive Days (Mandatory)

At least 12 testers must have been opted in continuously for the 14 days before you apply for production access.

> Note: Google may ask for more testing if tester engagement is insufficient. Launching the app regularly over those 14 days is safer than installing it once and never opening it.

3. Tester Engagement

Google may ask for more testing if you had fewer than 12 opted-in testers or insufficient tester engagement. The production access questionnaire also asks how your closed test went.

4. Technical Requirements

• Android App Bundle (.aab): The same format used for production
• Signed release build: A release build, not a debug build
• Target API level: Meet Google Play's current target API level requirement (targetSdk 36 or 37 and minSdk 33 or lower if you use Doply)
• Permission policy: Request only the permissions you need

The Full Android Closed Testing Process

Step 1: Establish a Test Plan

Set Testing Goals

• Core feature testing: Verify that key features work correctly
• Compatibility testing: Verify the app works across various devices and Android versions
• Performance testing: Confirm the app's performance is at an acceptable level
• Usability testing: Confirm users can use the app easily

Plan the Test Schedule

• Total testing period: At least 14 days (18 days recommended)
• Tester recruitment period: Begin recruiting one week in advance
• Test execution period: Continuous execution over 14 days
• Feedback collection period: Ongoing collection throughout the entire period

Step 2: Recruit Testers

Traditional Tester Recruitment Methods

1. Leverage acquaintances: Ask family, friends, and colleagues

2. Use communities: Developer communities, Reddit, Facebook groups

3. Social media: Twitter, Instagram, LinkedIn

4. Paid tester platforms: UserTesting, Testbirds

Problems with Traditional Methods

• Time-consuming: Finding testers can take several weeks
• Uncertainty: No guarantee that recruited testers will actually participate
• Management burden: Significant time spent managing and communicating with testers
• Hard to sustain for 14 days: Difficult to keep testers continuously launching the app for 14 days

Step 3: Configure Play Console

Create a Closed Testing Track

1. Open Google Play Console

2. Select your app > Testing and releases > Closed testing

3. Click Create new track

4. Enter a track name (e.g., 'Closed Testing Track 1')

5. Create the track

Set Up a Tester Group

1. Open the track's Testers tab

2. Choose how to add testers: an email list (CSV upload supported) or a Google Group

3. Enter the tester email list

4. Share the opt-in link with testers (Play Console does not email them automatically)

Distribute the App

1. Select the track > click Create new release

2. Upload the Android App Bundle (.aab) file

3. Enter release notes

4. Select countries/regions (include South Korea if you use Doply)

5. Send for review and publish (the opt-in link works only once the release is Published)

Step 4: Run and Monitor the Test

Google Play Console Monitoring

You can check the following information in Google Play Console:

• Number of testers: The number of testers who are currently opted in
• Crash reports: ANR and crash status
• User feedback: Feedback from testers
• Install statistics: Daily install counts

Additional Monitoring Tools

• Firebase Crashlytics: Real-time crash reporting
• Google Analytics: User behavior analysis
• Performance Monitoring: App performance monitoring

Step 5: Prepare for the Production Release

Pre-Launch Checklist

Production Release

1. Apply for production access: Apply from the Play Console Dashboard and answer the questionnaire (closed test, app, production readiness). Review usually takes 7 days or less

2. Upload the app bundle: Upload the production Android App Bundle

3. Store listing information: Prepare the app description, screenshots, icon, etc.

4. Release: Release to production once access is granted

Automating Android Closed Testing: The Doply Solution

The traditional Android Closed Testing approach takes a great deal of time and effort. Doply fully automates this process.

Automation Features Doply Provides

1. Automatically Secure 12+ Testers

Doply provides at least 14 (usually 16) automated testers.

• Testing starts right after payment (24/7, all year round)
• More testers than Google's 12-tester minimum, leaving a buffer
• No tester recruitment needed

2. Automatically Meet the 14-Day Testing Period

Doply runs tests automatically every day for 18 days.

• App launch jobs start at 3 AM KST every day, then run automatically
• Kept running for 18 days (14 required + 4-day buffer)
• No developer intervention required

3. Testing on 36 Real Android Devices

Real devices are used, not emulators.

• Real Samsung Galaxy devices
• Android 13 and 14 devices (your app's minSdk must be 33 or lower)
• Conditions similar to a real usage environment

4. Automatic Update Checks

When a new version is released, it is detected and installed automatically.

• Update check jobs run between midnight and 1 AM KST every day
• Automatic installation when a new version is found
• No manual checks needed

5. Transparent Progress

You can monitor testing progress in real time on the dashboard.

• Detailed logs provided
• A draft of your production access questionnaire
• Per-device testing status

How to Use Doply

Step 1: Download the Tester CSV File

Download the CSV file of Doply tester accounts from the Doply dashboard.

Step 2: Register Testers in Play Console

Upload the CSV file to your closed testing track's tester list in Google Play Console. Doply's tester accounts are Korean, so South Korea must be included in the track's countries/regions (you can exclude it from production).

Step 3: Register Your App in Doply

Enter your app's install link or package name in Doply.

Step 4: Compatibility Check

Doply automatically checks how many of its devices can install your app (almost instantly). The service is available when 14 or more devices can install it. Your minSdk must be 33 or lower, and paid apps need a 100% discount promotion during the test (do not switch the app to free; a free app cannot be made paid again).

Step 5: Pay and Press Install

After payment, press Install to start installing your app on Doply's devices. The status changes to Testing once the app is installed on 12 or more devices.

Step 6: Monitor Progress

You can check testing progress and testing logs on the dashboard. We recommend shipping at least 2 updates during the test (ideally 3–4, every 3–4 days); if you update 2 or more times, the test period can be extended for free. When the test ends, Doply prepares a draft of your production access questionnaire.

Doply Pricing

Doply offers a single plan of $6.99/app (excluding tax) for individuals and sole proprietors.

• 14+ testers (usually 16)
• 18-day testing period
• 36 real Android devices
• Daily update checks and app launches
• Testing logs and a draft of your production access questionnaire

Requirements: include South Korea in your closed testing track's countries (production can exclude it), minSdk 33 or lower, paid apps on a 100% discount promotion during the test (not switched to free), and no adult verification at install. You get a full refund if you never press Install, if the app is not installed on 12 or more devices, or if the service fails (TWA apps are not eligible for refunds). Contact: [email protected]

Best Practices for Android Closed Testing

1. Plan Thoroughly

• Clear goals: Clearly define what to test
• Test scenarios: Write specific test scenarios
• Success criteria: Set the criteria for a successful test

2. Test on a Variety of Devices

• Popular devices: Prioritize devices with high market share
• Varied screens: Test small, medium, and large screens alike
• Android versions: Test both the latest and older versions

3. Continuous Monitoring

• Daily checks: Check testing progress every day
• Bug reports: Immediately report bugs you find
• Feedback collection: Continuously gather tester feedback

4. Respond Quickly

• Bug fixes: Fix discovered bugs immediately
• Update releases: Roll out fixed versions quickly
• Communication: Share changes with testers

Frequently Asked Questions About Android Closed Testing

Q: What's the difference between Android closed testing and internal testing?

A: For personal developer accounts created after November 13, 2023, closed testing is where you need 12+ testers opted in for 14 consecutive days before applying for production access. Internal testing lets you add up to 100 testers, but it doesn't count toward this requirement.

Q: How long does it take to secure 12 testers?

A: Recruiting on your own can take several weeks. With Doply, testing starts right after payment, 24/7.

Q: Can the 14-day testing period be shortened?

A: No — per Google Play policy, the 14-day testing period is mandatory. However, with Doply, testing runs continuously for those 14 days, so you can use the period efficiently.

Q: Can I update the app during testing?

A: Yes. With Doply, new versions are detected and installed automatically, making update management easy. Google also recommends updating your app during closed testing. We recommend at least 2 updates (ideally 3–4, every 3–4 days); if you update 2 or more times, the test period can be extended for free.

Q: Which devices should I test on?

A: You should test on devices with high market share and a range of screen sizes. With Doply, your app runs automatically on available devices from a pool of 36 real devices (Android 13 and 14).

Conclusion: A Successful Android Closed Testing Strategy

Android Closed Testing is an essential step to successfully launch an app on Google Play. The traditional approach demands considerable time and effort, but with Doply you can fully automate the process.

Advantages of Using Doply

• Save time: At least 14 testers (usually 16) with no recruiting
• Built-in buffer: The test runs for 18 days (14 required + 4-day buffer)
• Diverse devices: Tested across 36 real Android devices
• Transparent progress: Check progress and testing logs on the dashboard
• Easy management: Proceeds automatically without developer intervention
• Cost-effective: $6.99/app (excluding tax) for individuals and sole proprietors

Next Steps

Start automating your Android Closed Testing with Doply today:

1. Try the Doply demo

2. Get started

3. Request a consultation

> Note: Google decides whether to grant production access, and Doply does not guarantee approval. You still need to ship updates and review your questionnaire answers yourself.

Doply is with you every step of the way to a successful app launch!

More Related Posts

• Complete Guide to Closed Testing Tracks
• How to Recruit Testers: Effective Strategies and Tools
• Android Closed Testers: Who to Find and How