golang-testing

Define a slice of anonymous structs with a name field plus inputs and expected outputs, then loop with t.Run(tt.name, func(t *testing.T)) for each case. Every case must have a descriptive name so failures identify the exact scenario.

Use a //go:build integration build tag at the top of the test file, before the package declaration, and run them with go test -tags=integration ./.... Avoid testing.Short() since those tests still compile and may attempt connections in normal runs.

Use go.uber.org/goleak by calling goleak.VerifyTestMain(m) in TestMain or defer goleak.VerifyNone(t) in individual tests. This fails the test if goroutines spawned during the test are still running at the end.

Build tags are preferred because testing.Short() still compiles the tests into the binary and requires a flag to skip them, while build-tagged files are completely excluded from compilation unless -tags=integration is passed.

Refactor the code to accept a clock interface and inject clockwork.NewFakeClock() in tests, advancing time with fakeClock.Advance(). For Go 1.25+, testing/synctest also provides deterministic synthetic time for goroutines and timers.

The helper function is missing t.Helper() as its first statement. Adding it marks the function as a test helper so the testing framework reports the caller's file and line instead of the helper's internal line.