Add Tester Emails to Your Closed Track

The order for registering the tester accounts LuneTest assigns on your Play Console closed track, publishing the change, and confirming the track has an installable release.

Find the account list

Once your application is submitted, the workspace shows the list of test accounts assigned to this test in the test-account area of the app detail screen. The list is given comma-separated, so it can be pasted into Play Console as it stands. You can copy it from the screen or download it as a file.

These are test accounts operated by LuneTest. Your own Google account password and verification codes are not needed at any step. Whether a service asks for account security details is one of the things to compare in choosing a Google Play closed testing service.

Open the closed track in Play Console

In Play Console, select the app and go to closed testing under the testing menu. If you already have a closed track in use, use that one.

If there is no track, create one and note its name. When the track named in your application and the track you actually registered the accounts on differ, the opt-in link will still open but nothing will be installable from it.

Paste the accounts into the tester list

On the track's testers tab, choose the email-list method and either create a new list or pick an existing one. Paste the supplied accounts in one go and save. Check that the number of accounts matches the number of devices in the product you ordered. The minimum tester count and continuous opt-in period Google states are covered in the 12 testers for 14 days checklist.

After saving, the change has to be published before it takes effect. An unpublished change stays on the Play Console screen only and is not applied on the store.

Confirm the track has an installable release

Registering testers does nothing if the track has no published release: there is nothing to install. Check that the latest release on the closed track is in a published state and that review has finished. If South Korea is excluded in the country settings, the Korean-profile devices cannot install the app.

If the app is paid, or cannot be entered without an in-app purchase, tell us through contact before you order. When you upload a new release after testing has started, the timing is covered in publishing an update during a closed test.

Confirm the registration went through

Once account registration and release publication are done, LuneTest checks from each account whether the opt-in link leads to an installable app. When that check finishes, the status on the app detail screen is updated.

After payment is confirmed and you request install and start, daily runs begin from that day. What each run row records is described in how to read the daily execution record. If the readiness check finds a problem, we tell you which item it was.

Where this usually goes wrong

The three most common cases are picking the wrong track, saving the list without publishing it, and a release still in review. Checking those three in order resolves most of them.

The order for confirming that the opt-in link belongs to the same track you registered the accounts on is in check the closed-test opt-in link. If the install still does not work, tell us through support on the app detail screen and we will reply with the time we checked and the state we observed.