Can you delete a closed testing track? Pausing, deleting releases, and the effect on your 14 days

1. You pause a track instead of deleting it

People often want to delete a closed testing track because they created it by mistake or want to end the test. But the Play Console Help Center article doesn’t describe any way to delete a testing track. To end a test, it tells you to click Pause track in the top right of the track page.

This applies both to the default ‘Closed testing - Alpha’ track and to tracks you created yourself. Just pause any track you’re not using.

2. What changes when you pause

• Testers stop receiving updates. Even if you upload a new version to that track, it won’t reach testers.
• The app they already installed stays on their device. It isn’t removed from testers’ phones.
• The test is treated as ended. If you were working toward the requirement, the test on that track stops there.

3. By reason for wanting to delete

People usually want to delete a track for one of four reasons. Each has a fix that doesn’t involve deleting the track.

• You uploaded the wrong release. According to Google’s documentation, you can only delete the latest release on a track, including draft releases and recently rejected releases. If the release is already published, bump the version code and upload a corrected release to the same track. Updates don’t break the 14 days (updating your app during closed testing).
• You want to clean up your tester list. Edit the list on the Testers tab. Uploading a CSV overwrites the existing addresses in that list, so upload a file that includes every address you want to keep. Accounts you remove from the list stop counting immediately, so don’t remove anyone during the 14 days (how to add testers).
• You created too many tracks. Keep the one you’re using and pause the rest. To avoid confusion about which track your testers are on, attach your tester list only to the track you’re using.
• It got mixed up with internal testing. Only closed testing counts toward the requirement, and accounts that joined internal testing can’t join closed testing for the same app (internal vs. closed vs. open testing).

4. After you launch

Even after you get production access and launch, there’s no need to delete your closed testing track. Google recommends continuing closed testing after you launch in production while you fix issues. Keep using it when you want to try new features with a small group of users first, and pause it if you won’t use it anymore.