---
title: "How to Configure Google Play Store Closed Testing"
source: "https://docs.nexcess.com/software/learndash/configure-google-play-closed-testing/"
description: "Introduction As of November 13, 2023, Google requires all new Individual Google Developer Accounts to complete a closed testing phase before publishing apps to…"
vertical: "Software"
area: "LearnDash"
date: "2025-09-23"
last_modified: "2025-09-23"
---

# How to Configure Google Play Store Closed Testing

## **Introduction**

  
As of **November 13, 2023**, Google requires all **new Individual Google Developer Accounts** to complete a **closed testing phase** before publishing apps to the Production track in the Play Store. This process includes having at least **12 internal testers** use the app for a minimum of **14 days** before you can unlock production access.

This requirement does not apply if your Google Developer Account was registered before November 13, 2023, or if you are using an **Organization Account**.

## **Create a Closed Testing Track**

1. Log into the **Google Play Console** and select your app.
2. In the left sidebar, go to **Release > Testing > Closed Testing**.
3. Choose from your active tracks:  
    
    - If an existing track is available, click **Manage Track**.
    - To create a new one, click **Create Track**.
4. Enter a **Track Name** and click **Create Track**.  
    
    - If this is your first time uploading a build to a test track, you may need to accept Google’s terms and conditions.
5. Go to the **Countries/Regions** tab and select where your app should be available for testing.  
    
    - To enable testing globally, check the box to select all countries.

## **Add Testers to Your Closed Test**

1. Go to the **Testers** tab.
2. Select an existing email list or click **Create Email List**.
3. Enter a **List Name** and add at least **12 email addresses**.
4. Click **Save Changes**, then **Create**.
5. Add a **Feedback URL** or email address so testers can send feedback. Click **Save**.
6. Click **Go to Overview** when prompted.

**Important:**

- Google requires a minimum of **12 testers** to opt in to your closed test.
- The **Copy Link** option for the test will only appear after Google approves your release.

## **Create a New Release for Closed Testing**

1. In your closed testing track, click **Create New Release**.
2. Under **App Bundles**, upload your **.aab** file or select one from your library.
3. Click **Add to Release**.
4. In **Release Details**, confirm the auto-filled version number and add **Release Notes**.
5. Click **Next**, then **Save**.
6. In the popup, click **Go to Overview**.
7. Click **Send Changes for Review**, then confirm again.

Google typically reviews a closed test release in **3–5 days**. Once approved, you’ll receive a **Test Link** to share with testers.

## **Configure License Testing**

While waiting for approval:

1. From the left sidebar, return to **All Apps**.
2. Under **Setup**, click **License Testing**.
3. Add license testers from your email lists and click **Save Changes**.

License Testing ensures only authorized testers can install and access the app.

## **Run the 14-Day Closed Testing Period**

Once your closed test release is approved:

1. Share the **Test Link** with your 12+ testers.
2. Testers must opt in and use the app for at least **14 days**.
3. Collect feedback to improve the app before production release.

## **Apply for Production Access**

After meeting the closed testing requirements:

1. In your app’s **Dashboard**, click **Apply for Production**.
2. Answer questions about:  
    
    - Your closed test process.
    - Your app/game details.
    - Production readiness.
3. Submit your request for review.

**Review Timeline:**

- Usually **7 days or less**.
- Once approved, the **Production** tab will be unlocked so you can upload your final build for public release.

## **After Gaining Production Access**

1. Create a release in the **Production** track.
2. Upload your final app build.
3. In WordPress, go to **Learndash App > Publishing Service > Google Play Store**.
4. Submit a publishing request.
5. The Publishing Team will manage the app submission and provide updates via email.

## **Troubleshooting and FAQs**

**Q: Do I need closed testing if I have an Organization Developer Account?  
 A: No, this applies only to **new Individual Developer Accounts**.

**Q: Can I skip the 14-day testing period?  
 A: No, Google enforces this for all new individual accounts.

**Q: What happens if I add fewer than 12 testers?  
 A: You will not meet Google’s requirement, and production access will remain locked.

**Q: When can I share the test link?  
 A: Only after Google approves your closed test release.

**Q: How long does Google take to review a closed test release?  
 A: Usually **3–5 days**, but it can take longer in some cases.

**Q: How long does production access review take?  
 A: Normally **7 days or less** after you apply for production.