Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jame581/godot-testing
Use when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C#
Passed 25 of 26 test cases with the skill, and 20 of 26 without it.
and 3 more in the full report
5 fixed20 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where in the project directory structure should unit test files be placed for GUT in a Godot project, and what prefix is mandatory for test file names?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies placing test files in res://tests/ or res://tests/unit/. | Missed | Passed |
| Specifies that GDScript test file names must begin with test_. | Passed | Passed |
The instructions your model reads when the skill loads.
This skill covers test-driven development (TDD) for Godot 4.3+ projects using GUT (Godot Unit Testing) and gdUnit4. It includes framework selection, full RED-GREEN-REFACTOR examples, test structure, running tests in CI, and common testing patterns.
Related skills: godot-code-review for review checklists, dependency-injection for test-friendly architecture, export-pipeline for CI/CD test automation.
| Feature | GUT | gdUnit4 |
|---|---|---|
| Language | GDScript-first, limited C# | GDScript + C# (first-class) |
| Install | AssetLib or git submodule | AssetLib or git submodule |
| Editor integration | Built-in GUT panel | Built-in inspector + panel |
| Mocking | double() / stub() API | mock() / spy() API |
| Scene testing | add_child_autofree() | auto_free() + scene runner |
| CI support | gut_cmdln.gd CLI script | gdunit4_runner CLI script |
| C# support | Minimal (GDScript wrappers only) | Native C# assertions + lifecycle |
| Maturity | Established (Godot 3 + 4) | Godot 4 focused, actively updated |
| Best for | Pure GDScript projects | Mixed GDScript/C# or C#-only |
Rule of thumb: Use GUT for GDScript-only projects. Use gdUnit4 for C# projects or when you need first-class C# support and scene runner utilities.
The standard Test-Driven Development cycle: write a failing test (RED), write minimal code to pass (GREEN), then refactor without breaking the test. Each step has its own discipline — don't skip RED (you'll write tests that pass trivially), and don't skip REFACTOR (technical debt compounds).
See references/tdd-workflow.md for a worked GDScript + C# example walking through all three steps on a HealthComponent.
res://
├── src/
│ └── components/
│ ├── health_component.gd
│ └── HealthComponent.cs
test cases passed, vs 20 / 26 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.