Drive a live Godot process to assert gameplay and UI state changes.
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill godot-e2e
Please help me install this Agent Skill. Skill: godot-e2e Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/core/godot-e2e Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill godot-e2e
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.
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).
High-intent search queries and answers about installing and using this skill.
To write end-to-end tests for a Godot game, use pytest with godot-e2e to launch a live Godot process, simulate input, and assert real gameplay state changes. This replaces manual trial-and-error loops with deterministic automated verification.
Yes, you can query Godot scene nodes dynamically using locator-based semantic querying. This feature finds nodes by group, name, type, or text with lazy re-resolution, ensuring your UI integration tests survive underlying scene-tree changes.
To capture Godot engine logs on test failure, use the expect() auto-retry matchers provided by godot-e2e. Every failing command automatically captures and attaches the relevant Godot engine logs, enabling self-diagnosing errors without manual inspection.
The best way to automate input simulation and scene transitions is by driving a live Godot instance via the godot-e2e TCP AutomationServer protocol. This allows tests to control the scene lifecycle, navigate scenes, and verify player behavior accurately.
Yes, true end-to-end gameplay tests require a live Godot instance rather than mocks. godot-e2e drives the actual Godot process to simulate input, handle frame and timing synchronization, and verify real UI state changes.
Godot UI tests break on scene tree changes if they rely on rigid node paths. Using locator-based semantic queries with lazy re-resolution finds nodes by group, name, or text, making tests robust against scene-tree modifications.
vzcoInject ARC Probe into a running Windows x64 process via TCP port 9998.
jomcgiDebug CI/CD failures by querying BuildBuddy invocations and fetching build logs.
PlayableIntelligenceAutomate end-to-end game QA testing with Playwright for boot, scenes, scoring, and visuals.
ZearainMaintains a persistent godot-mcp session to inspect and edit Godot 4.x scenes, nodes, and tests.
