You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# If FIPS=true unit tests need microsoft/go + OpenSSL with FIPS
224
225
.PHONY: test-unit
225
226
test-unit: prepare-test-context ## - Run unit tests only
226
-
set -o pipefail; go test${GO_TEST_FLAG} -tags=$(GOBUILDTAGS) -v -race -coverprofile=build/coverage-${OS_NAME}.out ./... | tee build/test-unit-${OS_NAME}.out
227
+
set -o pipefail;${GOFIPSEXPERIMENT} go test${GO_TEST_FLAG} -tags=$(GOBUILDTAGS) -v -race -coverprofile=build/coverage-${OS_NAME}.out ./... | tee build/test-unit-${OS_NAME}.out
228
+
229
+
# FIPS unit tests are meant to use go v1.24 to check FIPS compliance.
230
+
# This check is very strict, and should be thought of as a static-code analysis tool.
231
+
.PHONY: test-unit-fips
232
+
test-unit-fips: prepare-test-context ## - Run unit tests with go 1.24's fips140=only for testing
233
+
set -o pipefail; GOFIPS140=latest GODEBUG=fips140=only go test${GO_TEST_FLAG} -tags=$(GOBUILDTAGS) -v -race -coverprofile=build/coverage-${OS_NAME}.out ./... | tee build/test-unit-fips-${OS_NAME}.out
227
234
228
235
.PHONY: benchmark
229
236
benchmark: prepare-test-context install-benchstat ## - Run benchmark tests only
0 commit comments