Go Testing

Write Go tests test-first, where each case proves one behaviour through the package's public API. Load the conventions-go skill too: it sets the style and linter rules for test code (testCases/tc, rr, noctx, scopeguard, comments, testify/mock), and wins where the two overlap. Before writing or changing tests, read TEST-CONTRACTS.md for what an assertion must protect.

Style. When asked for unit tests, ask whether the user wants table-driven tests (the default) or f-tests, a local helper f called from named subtests.

Test-first in Go. A test written before its types exist fails to compile, which doesn't count as red. So: