Testing & Testers7 min read

How to Remove Closed Testing on Google Play

You can’t delete a closed testing track, but after production access you can end the test: how to pause it, what testers see, and what to keep for later.

Ahmed Akash
Ahmed Akash

Need testers who stay active for all 14 days?

TesterBee matches you with 12 real Android testers in under 24 hours. Refund if Google rejects you over tester engagement.

Get 12 testers
On this page
  1. 01Can you delete closed testing on Google Play?
  2. 02Wait for production access first
  3. 03How to pause your closed testing track
  4. 04What your testers see after you pause
  5. 05Check your version code before you pause
  6. 06Pause, keep or reuse: what to do with your testers
  7. 07Frequently Asked Questions
  8. 08Sources

You can’t delete a closed testing track in Play Console. Google gives you one way to end a test: pause the track. It takes about a minute, but two things decide whether it’s safe to do today: whether production access has actually been granted, and whether your production build has a higher version code than the build your testers are on.

Our advice is to leave the closed test exactly as it is until Google’s approval email arrives. If Google asks for more testing, you’ll need the same testers still opted in. Across the 1,500+ closed testing campaigns TesterBee has analyzed, 91% of apps refused on the first application were approved on the second attempt after addressing the reason Google gave, and that second attempt runs on the closed test you already have.

Can you delete closed testing on Google Play?

No. Play Console Help describes ending a test by pausing its track, not by deleting it. Once a test is paused, Google says testers stop receiving updates, but the app stays installed on their phones. Your store listing, your production release and your production users are not touched.

That also means removing closed testing rarely needs more than the pause. The tester list stays in Play Console, which is useful: if you run another test on the same app later, the people are already there.

Wait for production access first

For personal developer accounts created after November 13, 2023, Google only opens production after a closed test with at least 12 testers who stayed opted in for 14 days in a row. When you apply, Google reviews the application, which usually takes seven days or less, and it can ask you to keep testing if there were fewer than 12 opted-in testers or if tester engagement was too low.

So the order matters:

  1. Apply for production access with the closed test still running.
  2. Wait for Google’s decision, which arrives by email to the account owner.
  3. Only after access is granted, decide what to do with the test.

Pausing earlier ends the test Google is judging. If the answer is that more testing is required, a tester who opted out and back in needs a fresh 14 consecutive days to count again. Our guides on applying for production access and how long Google’s review takes cover that stage.

How to pause your closed testing track

These are the steps in Play Console Help, with the current menu names:

  1. Sign in to Play Console and select the app.
  2. Go to Test and release > Testing > Closed testing.
  3. Find the closed testing track you want to end.
  4. Click Pause track.

If the app also has an internal or open test running, each one is paused from its own page under Test and release > Testing. Pause only the tracks you are finished with.

What your testers see after you pause

Nothing disappears from their phones. Google’s help says the app stays installed and the test version simply stops receiving updates. From there, testers reach your public app in one of two ways:

  • Automatically. Google Play gives each device the highest version code it is eligible for, and every user is eligible for production. As soon as your production release has a higher version code than the test build a tester installed, it arrives as a normal update.
  • By leaving the beta. A tester can leave your beta program from the Play Store and install the public version. Google warns that leaving and uninstalling a beta app can lose progress and customizations, which matters for any app that keeps data on the phone.

Which of the two happens depends on one number, covered next.

Check your version code before you pause

This is the step most guides skip. Android uses an app’s versionCode as its internal version number, and it exists to stop a lower version replacing a higher one. A tester whose phone has a closed-test build with a higher version code than production stays on that build: once the track is paused it gets no more updates, and the production version can’t replace it until you publish something higher. Leaving the beta doesn’t help either, because getting the public version would then mean uninstalling, the step Google warns can lose data.

Before pausing, compare the version code of the latest closed-test build with the one live in production:

  • If production is equal or higher, pause the track. Testers end up on your public app on their own.
  • If the closed-test build is higher, publish your next production update with a version code above it first, then pause.

If you promoted the same build you tested, the numbers already match and there is nothing to do.

Pause, keep or reuse: what to do with your testers

Your situationWhat we’d do
Production access granted, no more testing plannedCheck the version code, then pause the closed track. Leave the tester list in place.
You want feedback on future updatesKeep a small closed list of trusted testers, or use open testing, which Google makes available once you have production access.
Google asked for more testingDon’t pause. Keep 12 or more testers opted in, fix the reason Google gave, and apply again.
You’re about to publish another appPlan its own closed test. Google’s requirement applies to each app, so the new one needs 12 testers opted in for 14 days of its own.

For the open testing route, see how internal, closed and open testing compare. If Google asked for more testing, start with the most common reasons a closed test falls short. And if your next app is close to launch, here is how to get 12 testers for its closed test.

Frequently Asked Questions

Will pausing closed testing affect my production app?

No. Pausing ends the test track only. Production is a separate track that every user is eligible for, so your public listing and your production users carry on as before.

Do testers have to stay opted in after production access?

Google’s 12-tester, 14-day requirement applies before you apply for production access. Once access is granted, nothing in Google’s testing requirements asks testers to stay. Keep them until the approval email arrives, in case Google asks for more testing.

Can I delete the closed testing track instead of pausing it?

Play Console Help describes ending a test by pausing the track, not deleting it. A paused track keeps its tester list, so it is ready if you test that app again.

Can the same testers join my next app’s closed test?

Yes. The same people can opt in to another app’s closed test, but the new app needs its own 12 testers opted in for 14 consecutive days before it can apply for production access.

Sources

Ahmed Akash
Ahmed Akash·Senior Full Stack Developer & Founder of TesterBee

Senior full stack developer specializing in Laravel, React, and Firebase. Helped 1,300+ Android developers pass Google Play Closed Testing and publish apps. Expert in Play Console, production access, and Android app publishing.

November 23, 2026 · 7 min readLinkedInGitHub

Get 12 testers into your closed test in 24 hours

Matched Android testers who open your app every day of the 14-day window, so your production access review has real engagement to look at.

Start your closed test