golang-testing

Table-driven unit tests in Go use named subtests with t.Parallel to structure cases and execute them concurrently, ensuring clear assertions and reliable coverage. This approach standardizes test cases for maintainability and faster CI execution.

Testing HTTP handlers in Go without a live server uses httptest.NewRecorder to capture responses directly. This allows you to assert status codes and response bodies efficiently while mocking dependencies at the consumer boundary.

Detecting goroutine leaks in Go integration tests involves using goleak within build-tagged integration suites. This verifies race-prone code safely and prevents flaky tests caused by lingering background goroutines.

Use package_test for black-box testing in Go when you need to verify external behavior without accessing internal package state. This layout enforces true API coverage and prevents unexported variables from creating false test dependencies.

Adding fuzz tests and benchmarks to a Go package involves creating Fuzz functions for critical inputs and benchmark functions with allocation tracking. This validates edge cases and measures performance impacts accurately.

This Go testing workflow supports testify suites where organized setup and teardown are needed. It applies testify alongside fake clocks and Example functions to maintain structured, documented, and reliable test environments.