golang-testing

Table-driven tests in Go use a struct slice of test cases with a name field, executed via t.Run to create named subtests. This pattern ensures every scenario is documented and runs as an isolated, identifiable test case within your suite.

Separate integration tests in Go using the //go:build integration build tag. This prevents integration code from compiling or running during normal unit test runs, keeping standard test execution fast and isolated from external systems.

Detect goroutine leaks in Go tests by integrating goleak for robust concurrency testing. It automatically verifies that goroutines are cleaned up after tests complete, ensuring deterministic behavior and preventing flaky test suites.

Flaky Go tests using t.Parallel often stem from shared state, improper synchronization, or goroutine leaks. Ensure independent unit tests are truly stateless, apply goleak for leak detection, and use deterministic time testing like testing/synctest.

Fuzzing and mocking can be combined in a Go test workflow to achieve testing completeness. Fuzzing validates edge-case inputs while mocks and interfaces isolate dependencies, supported by executable Examples and coverage workflows.

This Go testing approach applies to reviewing PR test changes and auditing for flakiness. It guides authors to write behavior-driven unit and integration tests, ensuring deterministic, production-ready patterns that scale reliably.