gdunit-driver

# gdUnit4 Test Driver $ARGUMENTS ## 1. Locate the Godot executable Read the path from the project's config file. This avoids hardcoding paths that differ per machine. ```bash # From the project root: python tools/agent_runtime.py godot_path ``` ## 2. Run tests The CLI runner across all supported versions (v4.x, v5.x, v6.x) is `addons/gdUnit4/bin/GdUnitCmdTool.gd`. The path uses capital-U `gdUnit4/` to match the upstream repo layout — Windows is case-insensitive but Godot's global script registry de-duplicates by exact path string, so a casing mismatch between the runner invocation and the on-disk directory triggers `Class "..." hides a global script class` parse errors and a non-zero exit. ```bash # Single file "<godot_path>" --headless -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd \ --add res://test/test_example.gd --ignoreHeadlessMode # Multiple files "<godot_path>" --headless -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd \ --add res://test/test_physics.gd --add res://test/test_spawner.gd \ --ignoreHeadlessMode # All tests in a directory "<godot_path>" --headless -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd \ --add res://test/ --ignoreHeadlessMode ``` Notes: - Include `--ignoreHeadlessMode` for headless runs. - Use `--add` to enqueue test files or directories (repeat the flag for multiples). - Runner path needs the `res://` prefix and the capital-U `addons/gdUnit4/` casing. - No `::method` syntax for single test methods — run the whole file instead. ### C# ...