Running Multiple Closed Tests for the Same App on Google Play

Play Console does not stop you at one closed test. Developers often want a second closed track: one for the 12-tester requirement window, another for a long-running partner group, or a private channel for builds that are not ready for the requirement-counting roster. Extra closed tracks are possible, but they split your testers and your attention, so it pays to understand the mechanics first.

How closed tracks fit together

Your first closed track is available by default as Testing > Closed testing for your app, and Play Console lets you create additional closed tracks alongside it. Each track is a separate channel: it has its own releases, its own tester list, its own opt-in link, and its own review queue. A release published to one closed track does not appear on another.

Which track counts toward the requirement

Splitting your strongest testers across two tracks is the classic mistake. Your most engaged people end up on a track that is not the one you point to when the milestone card asks about testing progress, while the designated track runs thin. Pick the track first, then put your best roster on it.

When a second closed track genuinely helps

• A partner or client group that needs early builds but must not disturb your 14-day window.
• A long-running soak test where the same build stays in the field for months.
• Experimental builds with a feature branch that your requirement testers should not see.
• Separating a legacy version of the app from a rewrite in progress.

The gotchas to expect

Multiple channels also multiply your regression surface, since every track now carries its own build that must behave. That is where a partner helps: AppsTestLab runs regression passes across parallel tracks so a fix intended for one channel does not quietly break another.