flame-harness-evaluator

Automate Flutter Flame game QA by enforcing a contract-based validation process that runs static analysis, executes tests, and performs simulator-based visual verification. This prevents deploying broken games by requiring actual gameplay verification rather than just code review.

Simulator-based visual verification mandates launching the game on a simulator to capture screenshots and verify the core gameplay loop. This mechanism prevents silent failures where code passes review but the game breaks visually or functionally.

Validate game assets and native configurations through automated hard gate checks that detect critical failures like missing assets, l10n errors, and non-compliant native settings. These gates act as a strict quality barrier before deployment.

Yes, you need a structured harness environment with defined configuration, state, and contract files. This setup is required to execute the mandatory hard gates and edge-case sweeps that validate the game build.

Yes, you can evaluate game feel, originality, and performance by enabling a strict quality scoring mode. This mode uses specialized agent teams to assess subjective and performance metrics beyond standard functional checks.

The best way is running an automated evaluator that validates builds against a predefined contract through static analysis, test execution, and simulator verification, generating a definitive QA verdict before deployment.