Google Play Closed Testing for Games: Getting 12 Players to Stay for 14 Days

Google Play now requires games to undergo a closed testing period before production access is granted. To qualify, developers must recruit at least 12 testers and keep them engaged for a full 14 days. The testing process is similar for apps, but games require a compelling reason for players to return each day. Short challenges, visible progress, and quick fixes are key to maintaining engagement throughout the test.

Developers must fill out three sections in the Play Console application: About your closed test, About your app/game, and About your production readiness. The closed test section must demonstrate that the game kept at least 12 players engaged for 14 continuous days, while the app/game section describes the game's unique features, and production readiness needs to show that any issues identified during testing have been addressed.

Google recommends recruiting testers who represent the target audience and suggests using game communities, Discord servers, or local gaming groups. Recruiters should be clear about the 14-day commitment and provide daily hooks, such as level challenges or new characters, to keep players engaged. A messaging group can serve as a shared leaderboard or chat, offering additional motivation for testers.

During the test, developers should ship mid-build updates with requested fixes and be prepared to answer questions about the game's difficulty, bugs, and performance issues on different devices. Technical checks should be conducted using real devices to cover the range of hardware that emulators may miss. The Play Console's pre-launch report should be reviewed for any crashes or performance warnings.

Before applying for production access, developers must ensure they have at least 12 testers who have been opted in for at least 14 days, have extra testers on standby, documented the features used by testers, summarized the received feedback, listed changes made based on the test, included test credentials, and confirmed that the content rating, target audience, and data safety settings accurately reflect the final app. Finally, there should be no crashes or empty screens in the production build.

Common mistakes include recruiting exactly 12 testers, running the test on the internal track, sharing an APK instead of using the opt-in link, and not making updates based on the test results. Developers should also avoid using friends who rarely play the game, buying reviews or ratings, and not offering compensation that violates Google Play policy. TestLancer offers a service to run a 14-day closed test and provide feedback, helping developers meet the new testing requirements efficiently.