How to Test an AI-Generated Game
A lightweight QA checklist for prompts, controls, edge cases and replayability.
Test generated games as untrusted software: verify every rule, reset path, device size, asset and external call rather than assuming a successful preview means the game is finished.
Start with a rule sheet
List each input, state transition, score event, win condition and loss condition. For every item, write one normal case and one edge case. This exposes vague design and gives you repeatable checks.
High-value tests
- Rapidly repeat every input and try simultaneous inputs.
- Pause, resize, rotate or background the app.
- Lose and replay ten times without refreshing.
- Test zero, maximum and negative-like boundary states.
- Run on the weakest target device and a slow connection.
- Inspect browser console and network requests where available.
Regression discipline
After each AI edit, retest the changed feature plus score, restart and save state. Keep versions so you can revert. A prompt that fixes one bug can silently break another system.
This page is a practical framework rather than a product-spec sheet. Validate platform-specific details before publishing a commercial project.