12 Testers for Godot: Google Play Closed Testing Guide
How Godot game developers can find 12 real testers, complete the 14-day requirement, and get production access on Google Play — complete guide for 2026.
1. Godot and Google Play Closed Testing
Godot has rapidly grown into one of the most popular open-source game engines, especially among indie and solo developers. But Google Play's Closed Testing requirement applies equally to Godot games: 12 real testers, 14 consecutive days, on physical Android devices. Godot's Android export pipeline is straightforward, but there are specific configurations you need to get right before uploading to Play Console.
2. Exporting Your Godot Game for Google Play
In Godot 4.x, go to Project → Export → Android. You need the Android SDK and OpenJDK installed (Godot's official docs cover this). Key export settings: enable Gradle Build, set Target SDK to 34+, enable ARM64 architecture, and configure a release keystore for signing. The export produces an AAB file ready for Play Console upload.
Godot tip
Use Play Asset Delivery for games larger than 200MB. Godot 4.3+ supports splitting assets into install-time and on-demand packs natively.
3. Play Console Closed Testing Setup
Upload your AAB to Testing → Closed Testing. Complete the store listing — Godot games need the same assets as any app: icon, feature graphic, screenshots, and a privacy policy. Create a Google Group with your 12 testers' emails. Share the opt-in URL and start the rollout once testers have accepted.
4. Getting 12 Testers for Your Godot Game
The Godot community is one of the most supportive in game development. Post your testing request in r/godot (200K+ members), the Godot Discord server, and Godot forums. Fellow Godot developers understand the publishing challenge and are often willing to test. For guaranteed results, TesterBee provides 12 verified testers who will actively play your game for 14 days on real Android devices.
5. 14-Day Testing for Godot Games
Push at least one update during the 14 days. Monitor crash rates in Play Console — Godot's GDScript can throw unhandled errors on specific Android hardware. Keep testers engaged with daily gameplay sessions of at least 5 minutes. Google's reviewers check for session consistency; a day with zero active users is a red flag.
6. Production Access for Godot Games
After 14 days of active testing with consistent DAU and at least one update, submit your production access application. Answer all 6 questions with specifics: mention tester feedback, describe the changes you made, and explain why your game is ready for the Play Store. Godot developers typically receive production access decisions within 3-7 days.
7. Common Godot Android Export Issues
Keystore configuration errors
Godot requires a properly configured debug.keystore or release.keystore. Generate one via keytool if you have not already.
ARM64 not in export template
Download the ARM64 export template in Godot's Asset Library. Without it, your game will not pass Play Console validation.
Gradle build fails
Ensure Android SDK platform 34 and build tools 34.0.0 are installed. Godot 4.3+ handles Gradle setup automatically.