godot-e2e

What problem does it solve?

It removes the slow, manual trial-and-error loop of testing gameplay and UI by letting you execute deterministic end-to-end tests against a real Godot project and get automatic engine-log diagnosis on failure.

Core Features & Use Cases

• Write true E2E gameplay + UI tests: simulate input, navigate scenes, and verify player/UI behavior using a live Godot instance rather than mocks.
• Locator-based semantic querying: find nodes by group/name/type/text (with lazy re-resolution) so tests survive scene-tree changes.
• Auto-retry assertions with engine logs: use expect() to poll until state matches, while every failing command captures the relevant Godot engine logs for self-diagnosing errors.
• Use case: verify that clicking a menu button transitions to the correct scene and that key UI labels display the expected text, while failing tests include the engine error logs that occurred during the action.

Quick Start

Instruct the agent to write a pytest test using godot-e2e that launches your project, performs one gameplay action (like input_action or a button click), then asserts a changed in-game state with expect() (for example, verifying a status label text after the click).