Run gdUnit4 tests for Godot projects and parse output into structured results.
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill gdunit-driver
Please help me install this Agent Skill. Skill: gdunit-driver Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/core/gdunit-driver Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill gdunit-driver
This Skill eliminates the slow, error-prone process of manually checking whether Godot gameplay logic and utilities behave correctly by running gdUnit4 tests and converting results into actionable structured output.
Use cases: after writing or modifying gameplay code, investigate failing assertions quickly, ensure new tests follow gdUnit4 conventions, and produce machine-readable test reports for automation.
Run the gdUnit4 test driver from your Godot project to execute your test files headlessly and get pass/fail status plus failure details with file locations.
High-intent search queries and answers about installing and using this skill.
Run gdUnit4 tests headlessly by executing GdUnitCmdTool.gd with res:// paths via the Godot executable to output structured pass/fail results for your GDScript or C# code.
The gdUnit4 test runner supports C# unit tests in Godot 4.x/v5.x/v6.x setups, executing them headlessly alongside GDScript files while requiring standard C# build prerequisites.
Unit tests fail in Godot CI pipelines if parsing does not strip ANSI codes or handle exit codes correctly; this driver converts raw runner output into machine-readable JUnit XML reports.
Debug failing Godot gameplay logic by running gdUnit4 tests to investigate failing assertions and receive structured results that include precise file:line context for the failures.
Scene-tree execution and async signal testing in gdUnit4 work by using SceneRunner to validate gameplay logic, handling single-file, multiple-file, and directory test discovery with appropriate timeout guidance.
minami110Execute GDUnit4 tests and generate JSON reports for Godot projects.
solace-illAnalyze CI logs and JUnit/XML results to detect flaky tests.
dragoscirjanDiagnose Godot 4 engine quirks and scene-generation pitfalls.
bingeli1379Automate Godot 4.3+ test-driven development workflows with GUT and gdUnit4.
