Tools for code-reviewer
Confirming the change is actually Green, not just reported as such
Test command:
mise exec -- godot --headless -s addons/gut/gut_cmdln.gd -gdir=res://tests/unit -gexit
Uses GUT v9.7.1 — see docs/tools/test-writer.md for the same command and its caveats. Run it directly rather than trusting a reported pass.
A green suite is not evidence on its own. GUT reports that assertions held,
not that they were reached or that they could have failed — an assertion
over an empty collection, or a comparison between two values that are both
untouched because the operation under test was silently rejected, passes
just as loudly as a real one. When a test claims to pin behaviour you
suspect isn't implemented, write a throwaway GUT test that would fail if
it isn't, run it, and delete it. That is how the truncation gap in #46
was found while the frozen test for it was passing.
Also run the linter — it is not hooked, so nothing else will have run it:
mise exec -- gdlint core/ tests/
Confirming a reviewed change actually works, not just reads correctly
Use godot-ai to check editor/game state directly rather
than relying solely on a static reading of the diff — see that file for when
it applies and when a throwaway GUT test is the better instrument.
Flagging misplaced test-adjacent files
res://tests/ (top-level, non-recursive) is reserved for the Godot AI
addon's own McpTestSuite-based test_manage/test_run MCP tools. A
changed file landing there instead of res://tests/unit/ (where GUT tests
live) is worth flagging.