Step 1: create the closed testing track

The test runs on a closed testing track of your app in the Play Console. Open “Test and release › Testing › Closed testing” and keep one track for the whole test.

J
Written By JordanLast updated 1 hour ago

What this step is for

Google asks personal developer accounts created after 13 November 2023 for a closed test before production. The 12 testers and their 14 days are counted on a closed testing track: internal testing doesn't count.

How to do it

  1. Open your app in the Play Console.
  2. Go to “Test and release › Testing › Closed testing”.
  3. Keep the track Google suggests, or create one. One is enough.
  4. In Peerbeta, click “Done” on the “Create the closed testing track” step.

The next steps all happen on this same track: the testers' group, the countries, then the release.

Common mistakes

  • Running the test on internal testing. It's a separate track: it doesn't count, and a tester enrolled there no longer gets the closed test.
  • Spreading testers over several closed tracks. Google doesn't say whether they add up: keep everyone on the track that holds your release.
  • Pausing the track during the 14 days. Pausing ends the test for testers: keep it running until Google gives you production access.

Was this helpful?

Your feedback shapes what we write next.