unit-test

# Go Unit Test Create and refine Go tests for this repository with table-driven cases and explicit bug-hunting rules. ## Quick Reference | When you need to… | Jump to | |---|---| | Quick tests for simple functions | Light mode — §Execution Modes | | Normal feature development | Standard mode (default) — §Execution Modes | | High-risk / release / concurrent code | Strict mode — §Execution Modes | | Fix or triage failing tests | §Test Execution Hardening | | Supplement coverage on existing code | §Coverage Gate Policy | | Know if a Killer Case is required | Standard + Strict modes: always required — §Killer Case | | Check Go version compatibility | §Go Version Gate | | Write a Killer Case | §Killer Case — Definition + load `references/killer-case-patterns.md` | ## Hard Rules - Name test files as `<target_file>_test.go`, co-located with source. - Assertion strategy (adapt to project): - **If project uses testify**: `require` for fatal preconditions, `assert` for value checks. - **If project uses standard library only**: use `t.Fatalf` for fatal preconditions, `t.Errorf` for value checks. Include got/want in messages: `t.Errorf("Name = %q, want %q", got, want)`. - **If project uses go-cmp**: use `cmp.Diff` for deep struct comparison. Prefer over field-by-field assertion for complex output. - **Detection**: Check existing `_test.go` files for `"github.com/stretchr/testify"` imports. Follow project convention. - Keep tests deterministic; isolate time, randomness, envir...