How to remove a closed testing track in Play Console

Short answer: you don't delete it, you pause it. Google's help describes one way to end a test: open the track, click Manage track, then Pause track near the top right. "After ending a test, testers do not receive updates, but the app will remain installed on their device" (Play Console Help). Google's documentation doesn't describe a delete button for testing tracks.

Before you click anything, check why you want the track gone. Most reasons have a better answer than pausing, and one of them can cost you your 14 days.

Stop: are you still in the 14 days?

If you haven't been granted production access yet, don't pause your closed track. Google's requirement is "a minimum of 12 testers who have been opted in continuously for at least 14 days", checked when you apply (Play Console Help). Pausing ends the test. Google's help doesn't say how a paused track affects the testers counted for the requirement, so don't make your application the experiment.

The same goes for moving testers to a "cleaner" track halfway through. Each tester's 14 days count from their opt-in to your closed test. Keep your 12 or more on one track until you're approved. Details in testers not counted.

Pick your situation

You got production access and want to tidy up

You don't have to remove anything. Testers in a closed test are eligible for both the Production and Closed testing tracks, and each device gets the highest version code it's eligible for. If your production release has a higher version code than the closed track, your testers simply get the production version (Play Console Help). Play Console will then show the closed track as superseded, which is expected.

There's a good reason to keep it: Google recommends you keep testing before publishing production updates (Play Console Help). Your closed testers are a ready-made beta group for the next version. See internal vs closed vs open testing for which track fits which job after launch.

You created an extra closed track by mistake

Google lets you create additional closed tracks with Create track, each with its own name and testers (Play Console Help). If you made one you don't need:

1. Go to Test and release > Testing > Closed testing.
2. Click Manage track next to the extra track.
3. Click Pause track at the top right.

The track stays in your list, but it no longer serves updates. Make sure your real testers and your release are on the other track.

You uploaded a bad build to the track

Pausing is the wrong tool. Google gives a way to discard a release, depending on its state (Play Console Help):

• Draft: click Discard draft release.
• Ready to send for review: click Discard release on the release summary.
• In review or Ready to publish: remove the changes from Publishing overview first, then click Discard release.
• Rejected: click Discard release on the rejected release summary.

You can only discard the latest release on a track. If the bad build is already published to testers, upload a fixed build with a higher version code. Google encourages exactly this kind of update during a closed test.

You want to remove some testers

Edit the tester side, not the track:

• Email list: remove the address from the list selected on the track's Testers tab, then save.
• Google Group: remove the member from the group.

Testers can also leave on their own from the Play Store app: Manage apps & devices > Beta, then Leave under "You're a beta tester" (Google Play Help).

During the 14 days, avoid removing testers you still need for the count.

You want the app off Google Play entirely

Pausing a testing track only stops updates on that track. To stop new users from finding the app, Google's option is to unpublish it: Test and release > Setup > Advanced settings, App Availability tab, Unpublish. Existing users keep the app and still receive updates. Google lists conditions first: you've accepted the latest Developer Distribution Agreement, the app has no outstanding errors (such as an unfinished content rating questionnaire), and managed publishing isn't active (Play Console Help).

After you pause

• Testers keep the app installed. Google doesn't say it uninstalls anything.
• They stop getting updates from that track.
• If you start testing on that track again later, check the Testers tab and the release before you share the link.

When you're ready to apply, the steps are in how to apply for production access.

When to contact Google

You rarely need support for this. Contact Google through the Contact us link in Play Console Help if a track you didn't create appears, if Pause track is missing or greyed out on a track you manage, or if testers still get a build from a paused track after several days. Include the package name and the track name. For how tracks fit into the whole requirement, see the Google Play closed testing guide.