Testing Strategy

--- title: "Testing Strategy" description: "Aurora's 3-layer testing strategy: unit tests, integration tests, and contract replay tests." icon: "test-tube" ---

Testing Strategy

Aurora uses a 3-layer testing strategy:

Layer 1: Unit Tests

Package-level tests that verify individual components in isolation.

go test ./internal/...          # All unit tests
go test ./internal/server       # Server package tests

Layer 2: Integration Tests

Tests that verify interactions between components with real dependencies (database, cache).

make test-race                  # With race detection
make test-e2e                   # End-to-end tests

Layer 3: Contract Replay Tests

Tests that verify behavior against recorded provider responses, ensuring compatibility across versions.

Test Organization

• Tests live alongside the code they test (_test.go files in the same package)
• Integration tests use build tags where needed
• E2E tests use in-process mock servers (no Docker dependency)

Coverage

make test-race    # Includes coverage output

Benchmark Tests

Gateway stack benchmarks are in internal/server/gateway_stack_bench_test.go:

go test ./internal/server -run "^$" -bench BenchmarkGatewayStack -benchtime 10s -benchmem

See Benchmark Setup for side-by-side comparison benchmarks.