Makefile: Disable test caching by using go test -count=1 #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The test-integration Make target clears the entire Go test cache, which is overly aggressive, especially when running
go test ./...
in other projects, causing all tests to re-run in those other projects after running the integration tests.Instead, use the idiomatic -count=1 flag to explicitly disable test caching.
This idiom is mentioned in the documentation [1]: "The idiomatic way to disable test caching explicitly is to use -count=1."
[1] https://pkg.go.dev/cmd/go#hdr-Test_packages