gds-agent-game-dev

Create a GameE2ETestFixture base class that loads your scene, then use a ScenarioBuilder for state setup, an InputSimulator for player actions, and AsyncAssert.WaitUntil for condition-based waits. Avoid WaitForSeconds as the primary synchronization method to prevent flaky tests.

Install the GUT plugin from the Asset Library, place tests under a tests/ directory with the test_ prefix, and run them headless via godot --headless -s addons/gut/gut_cmdln.gd. Use before_each and after_each for setup and queue_free nodes to avoid orphan warnings.

Unit tests verify single-class logic in under 10ms, integration tests check system interactions like combat plus inventory, and E2E tests validate complete player journeys such as a full combat encounter. E2E tests sit between integration tests and manual playtesting in the test pyramid.

Yes, it covers Unreal's Automation Framework with FFunctionalTest actors, latent automation commands, and Gauntlet for extended E2E suites. It also includes certification test examples for platform requirements like suspend/resume handling.

Flakiness usually comes from WaitForSeconds-based timing, shared state between tests, or reliance on animation and frame timing. Use explicit condition waits, isolate each test with full cleanup, and seed random number generators for determinism.

Cover suspend/resume handling, controller disconnect, user switching, save data validation, and network loss scenarios. PlayStation TRC, Xbox XR, and Nintendo guidelines each define critical requirements that must pass before store submission.