Testing

Developer-oriented notes for local loops. For deployment evidence classification, use the dedicated Testing section:

• Testing overview
• Test strategy
• Test matrix
• Live E2E
• Release acceptance checklist
• Windows Service E2E
• Linux systemd E2E
• Docker E2E
• Known untested scenarios

Baseline commands

text go fmt ./... go vet ./... go test ./... -count=1 go build ./cmd/iqv-integration-api

Optional / environment-dependent:

text go test -race ./... # SKIPPED without cgo MONGODB_INTEGRATION_TEST_URI=... go test ./internal/... -count=1 # CONDITIONAL integration

Guidelines:

• Prefer real assertions over smoke-only checks.
• Use interface fakes for MongoDB health unit tests.
• Do not mock the exact function under test into a no-op success path in production code.
• Do not connect tests to production systems.
• Unit AUTOMATED PASS is not live deployment PASS.