If your app needs a login, or sells something, your testers need extra instructions. Without them, they get stuck at the first screen, or they spend real money by mistake. Both waste your 14 days. This guide gives you messages for each case, and what Google says. The sources are Google's testing requirements and its page on setting up a test.

If your app needs a login

Google says reviewers need valid, working credentials. Your testers need them too. See login details for Google's review.

Message to send:

Your app, [app name], needs an account. Please use this test account and not your own: Email: [test email] Password: [test password] If you see a code or a "verify" screen, tell me and I will send a code. Please do not change the password. If the login does not work, write to [your contact] with a screenshot.

Tips:

• Use a test account that is not your personal one.
• If your app allows only one session per account, create one account per tester.
• If a verification step blocks testers, remove it for the test accounts.

If your app is paid

Google says that when you test a paid app using an open or closed test, testers still need to purchase it. Plan for that:

[app name] is a paid app, so you will see the normal purchase step. Please write to me before you buy, and I will tell you how to get it for testing.

Check Google's page on setting up a test for the options, because they change.

If your app has purchases or subscriptions

Be careful here. Two points from Google:

• Google says test devices in the pre-launch report cannot make purchases, so tests behind a purchase are limited. See the pre-launch report guide.
• Google says that if you change your app's pricing, it affects your app's current and future versions across all tracks, so do not experiment with prices during the test.

Message to send:

Please do not make real purchases while testing. If you want to test the purchase screen, open it and tell me if the screen looks right (price, text, buttons), then go back. I will tell you if there is a safe way to complete a test purchase.

If you set up a safe way to test purchases, describe it step by step, and tell testers exactly which account to use.

If the app uses personal data

Please do not enter real personal data, such as real addresses, ID numbers or payment cards. Use made-up details. If a screen asks for something you cannot invent, tell me.

Put it in one message

Combine the parts you need with the message template for testers. Keep the message short, and put the 14-day opt-in reminder at the top.

If you use ClosedTest

Our setup form asks whether your app needs a login, and for the test details. Use a dedicated test account. Never send us your Play Console password. We only need your opt-in link.

ClosedTest is an independent service and is not affiliated with Google.