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
225
224
.PHONY: test-unit
226
225
test-unit: prepare-test-context ## - Run unit tests only
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
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
228
227
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
228
+
.PHONY: test-fips-provider-unit
229
+
test-fips-provider-unit: prepare-test-context ## - Run unit tests with GOEXPERIMENT=systemcrypto to check that system FIPS provider works
230
+
set -o pipefail; GOEXPERIMENT=systemcrypto CGO_ENABLED=1 go test${GO_TEST_FLAG} -tags=$(GOBUILDTAGS) -v -race -coverprofile=build/coverage-${OS_NAME}.out ./... | tee build/test-unit-${OS_NAME}.out
234
231
235
232
.PHONY: benchmark
236
233
benchmark: prepare-test-context ## - Run benchmark tests only
0 commit comments