Configure Google Play Store Closed Testing for MemberPress App

App testing with selected users before public release. New individual Google Developer accounts created after November 13, 2023, must complete closed testing requirements before production access. This document explains how to create closed testing tracks, add testers, manage releases, and apply for production access.

Understanding Closed Testing Requirements

Google Play Store requires closed testing completion for new individual developer accounts registered after November 13, 2023. Closed testing involves at least 12 testers using the app for a minimum of 14 consecutive days. Production track access unlocks only after successful closed testing completion and approval.

Organization developer accounts are exempt from closed testing requirements. Developer accounts registered before November 13, 2023, are also exempt from mandatory closed testing. Individual accounts created after the requirement date must complete closed testing before production publishing.

Creating Closed Testing Track

Closed testing track creation establishes the testing environment for pre-release app distribution.

1. Log in to Google Play Console at play.google.com/console.

2. Select the app from the apps list.
3. Navigate to Release > Testing > Closed Testing in the left sidebar.

4. Review available active testing tracks.
5. Click Manage Track if an existing track is available.

6. Click Create Track if creating a new testing track.

7. Enter a descriptive name in the Track Name field.

8. Click Create Track to finalize track creation.

9. Navigate to the Countries/Regions tab.
10. Click Add Countries/Regions.

11. Select countries where the app should be available for testing.
12. Check the box to select all countries for global testing availability.

Adding Testers to Closed Test

Tester addition enables specific users to access and test the app.

1. Navigate to the Testers tab in the closed testing track.
2. Review existing email lists

3. Or click Create Email List.

4. Enter a descriptive name in the List Name field.

5. Add at least 12 email addresses to the tester list, or upload a CSV list.

6. Click Save Changes to store the email list.
7. Click Create to finalize the list creation.
8. Enter a Feedback URL or email address for tester feedback submission.

9. Click Save to store feedback information.
10. Click Go to Overview when prompted.

Note: Minimum 12 testers must opt in to the closed test to meet Google's requirements. The test link for sharing becomes available only after Google approves the release.

Creating New Release for Closed Testing

Release creation prepares the app build for tester distribution.

1. Navigate to the closed testing track in Google Play Console.
2. Click the Create New Release button.

3. Scroll to the App Bundles section.
4. Click Upload to select the AAB file from the device.

5. Alternatively, select an existing AAB from the library.
6. Click Add to Release after selecting the build.
7. Navigate to the Release Details section.
8. Verify the auto-filled version number is correct.
9. Enter Release Notes describing changes or features.
10. Click Next to proceed to review.
11. Click Save to store release information.
12. Click Go to Overview in the confirmation pop-up.
13. Click Send Changes for Review to submit for approval.
14. Confirm submission in the confirmation dialog.

Note: Google typically reviews closed test releases within 3-5 days. The test link becomes available after approval for distribution to testers.

Configuring License Testing

License testing restricts app access to authorized testers during the testing period.

1. Navigate to All Apps in the Google Play Console left sidebar.
2. Click Settings > License Testing in the navigation.

3. Select tester email lists from available options.

4. Click Save Changes to finalize license testing configuration.

License testing ensures only authorized testers can install and access the app during the closed testing phase.

Running 14-Day Closed Testing Period

Testing period execution collects feedback and validates app functionality before production.

1. Wait for Google approval confirmation of the closed test release.
2. Copy the test link from the closed testing track overview.
3. Share the test link with all 12 or more testers via email.
4. Verify testers opt in to the closed test through the link.
5. Monitor tester engagement throughout the 14-day minimum period.
6. Collect feedback from testers through the designated feedback channel.
7. Review feedback to identify improvements before production release.
8. Ensure at least 12 testers actively use the app for 14 consecutive days.

Note: The 14-day testing period is mandatory for new individual developer accounts. The testing period cannot be shortened or skipped.

Applying for Production Access

Production access application requests unlock the production track for public app release.

1. Navigate to the app dashboard in Google Play Console after completing testing requirements.
2. Click the Apply for Production button.
3. Review the production access application questionnaire.
4. Answer questions about the closed test process and results.
5. Provide details about app or game functionality and features.
6. Confirm production readiness and quality standards.
7. Click Submit to send the application for Google review.
8. Wait for Google's review decision on production access.

Google typically reviews production access applications within 7 days or less. Production tab unlocks after approval, enabling public release preparation.

Publishing After Production Access

Production release preparation follows production access approval.

1. Navigate to the Production track in Google Play Console after approval.
2. Click Create New Release in the production track.
3. Upload the final app build AAB file.
4. Complete release details, including version information and release notes.
5. Save the production release configuration.
6. Navigate to Dashboard > MP App > Publishing Service > Google Play Store in WordPress.
7. Click Submit to create a publishing request.
8. The Publishing Team manages app submission to the Google Play Store.
9. Monitor email for updates from the Publishing Team on submission status.

Publishing Team handles the final app submission and communication with the Google Play Store review team.