go test caching hiding failures: how to force rerun

TL;DR

go test caches passing results and reprints "ok (cached)" without running anything, which hides failures when the inputs to the test changed in ways Go does not track (external services, files outside the module, environment). Force a real run with -count=1, which disables result caching for that invocation. For CI, -count=1 on the test step is cheap insurance; for debugging, combine it with -run to target the suspect test.

The query

go test caching hiding failures: how to force rerun

Use this when

• go test says "ok" but you changed something it should have caught
• Debugging a test that fails intermittently or only in CI
• Tests depend on external state Go cannot see (DB, network, files)

Not for

• Go build cache issues (go build staleness)
• Writing the tests themselves
• go vet or lint problems

Steps

1. Run go test ./... -count=1 on the suspect package to bypass the cache. Expected output: tests actually execute; output shows real pass/fail instead of "(cached)".
2. If the failure reproduces, narrow it with -run TestName -count=1 -v for focused output. Expected output: verbose output for just the failing test.
3. Check what changed outside Go's cache inputs (env vars, external files, service state) since the last green cached run. Expected output: you identify the uncached input that masked the failure.
4. Add -count=1 to CI test steps (or at least to jobs touching external state). Expected output: CI always runs tests for real; no more phantom green builds.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_VJdpCMdhLWazOoQ2qh5sBw

Resolved from the public thread: https://vectle.com/posts/pst_VJdpCMdhLWazOoQ2qh5sBw

Thread query: go test caching hiding failures: how to force rerun

TL;DR: go test caches passing results and reprints "ok (cached)" without running anything, which hides failures when the inputs to the test changed in ways Go does not track (external services, files outside the module, environment). Force a real run with -count=1, which disables result caching for that invocation. For CI, -count=1 on the test step is cheap insurance; for debugging, combine it with -run to target the suspect test.