Google Play closed testing FAQ

LuneTest does not request a Google password, two-step verification code, recovery code, or Play Console administrator access.

Google controls policy enforcement, test recognition, and production-access decisions. LuneTest reports the execution facts it observes without claiming an approval outcome.

What do I prepare before ordering?

Publish an installable release on the Google Play closed track, add the supplied tester accounts to that same track, and make the release available to testers in South Korea (KR).

How long does the managed window last?

One order covers 15 tester accounts and a 15-day managed window. You may request one three-day extension for the same order before that window ends.

What evidence can I review?

Your workspace records the installation and launch facts LuneTest observes, including date, installed version, outcome, and retained screenshots.

Do you need my Google password?

No. LuneTest does not request Google passwords, two-step verification codes, recovery codes, or Play Console administrator access.

Will testers write ratings or reviews?

No. The service does not include human usability research, public reviews, star ratings, or fabricated feedback.

What if I publish an update?

Keep the release available on the same closed track. LuneTest checks the installed version during subsequent runs and records the version it observes.

How is the global checkout confirmed?

Paddle shows the country-localized total before payment. LuneTest treats the signed Paddle webhook, not a browser redirect, as the payment confirmation.

Does this guarantee Google approval?

No. Google controls policy enforcement, test recognition, and production-access decisions. LuneTest reports observed execution facts without claiming an approval outcome.