Game Testing 2D

Test authoritative rules at the narrowest deterministic boundary, then add engine and runtime evidence where integration matters.

Start from the failure surface

1. Read repository instructions, the behavior contract, and current tests.
2. Detect engine version, language, runner, physics backend, target platforms, and CI limitations.
3. Reproduce the behavior before changing production code when diagnosing a bug.
4. Classify the needed evidence: pure rule, engine integration, rendered output, exported build, or human play.

Load references

• Read testing-strategy.md for test layers, deterministic harnesses, replays, maps, and visual checks.
• For Phaser, also read phaser.md.
• For Godot, also read godot.md.
• If installed, compose with $game-dev-2d-gameplay for behavior ownership and $release-game-dev-2d for artifact smoke tests. Otherwise derive the needed contracts from the project and complete this testing workflow independently.