Claude-skill-registry gdunit4-test-runner
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/gdunit4-test-runner" ~/.claude/skills/majiayu000-claude-skill-registry-gdunit4-test-runner && rm -rf "$T"
manifest:
skills/data/gdunit4-test-runner/SKILL.mdsource content
GDScript Test
Run GDUnit4 tests using the test wrapper script.
When to Use
- After implementing new features
- After fixing bugs
- After modifying GDScript files
- When you need to verify test coverage
- When running CI/CD validation locally
Test Execution
Run tests using the wrapper script included in this skill.
Run All Tests
${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/run_test.sh
Scans entire project for tests.
Run Specific Test File
${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/run_test.sh tests/test_foo.gd
Run Multiple Tests
${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/run_test.sh tests/test_foo.gd tests/test_bar.gd
Run Tests in Directory
${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/run_test.sh tests/application/
Verbose Mode
${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/run_test.sh -v
Shows all Godot logs (useful for debugging test issues).
Understanding Results
The script outputs test results in JSON format for easy parsing.
Success
{ "summary": { "total": 186, "passed": 186, "failed": 0, "crashed": false, "status": "passed" }, "failures": [] }
Failure
{ "summary": { "total": 10, "passed": 8, "failed": 2, "crashed": false, "status": "failed" }, "failures": [ { "class": "TestClassName", "method": "test_method_name", "file": "res://tests/test_file.gd", "line": 42, "expected": "expected_value", "actual": "actual_value", "message": "FAILED: res://tests/test_file.gd:42" } ] }
Crash
{ "summary": { "total": 5, "passed": 3, "failed": 0, "crashed": true, "status": "crashed" }, "crash_details": { "crash_info": "handle_crash: Program crashed with signal 11\n...", "script_errors": "SCRIPT ERROR: Parse Error: ...\n...", "engine_errors": "ERROR: Failed to load script ...\n..." }, "failures": [] }
Godot crashed during test execution. Only tests completed before crash are reported.
The
crash_details object includes:
: Crash signal and C++ backtrace (if available)crash_info
: GDScript parse errors with file paths and line numbersscript_errors
: Engine-level errors (resource loading failures, etc.)engine_errors
Exit Codes
- 0: All tests passed
- 1: Some tests failed
- 2: Crash or error (e.g., Godot crashed, report file not found)
Notes
- Script automatically changes to project root before running tests
- Test reports are saved in
directoryreports/ - Uses gdUnit4 framework (configured in project.godot)
- Compatible with CI/CD environments