Prepare evidence, not guesses.

Closed-testing launch checklist

1. Have a testable release available in the intended closed track.
2. Make sure the package name and opt-in URL match the same app and track.
3. Add the assigned tester emails to the correct tester list.
4. Ask testers to join using the same Google accounts that were listed.
5. Use TestTwelve monitoring as an internal operational signal, not as a substitute for Google Play Console status.

If Google asks for more testing

Review the actual tester continuity, whether testers were able to install and use the app, whether the testing track and list were configured correctly, and whether the production-access answers accurately described the testing that took place. If the original campaign had an inactive tester, a replacement tester may need their own full continuity period.

Prepare for the production-access questionnaire

When Google asks about your closed test, base your answers on what actually happened. Useful evidence can include the testing dates, number of participating testers, the workflows they exercised, feedback received, bugs or usability issues found, and changes you made as a result.

Keep account credentials private

Never give TestTwelve or a tester your Play Console password, Google password, OTP, recovery code or payment credentials. The platform is designed around app details, tester coordination and monitoring—not account takeover.