golang-testing

Table-driven tests in Go use a slice of structs to define test cases, iterating over them with t.Run to create named subtests. This pattern promotes clear, deterministic test cases and enables easy parallelization where applicable for reliable validation.

Mocking dependencies in Go integration tests is best handled using testify to isolate dependencies and validate interactions. This approach allows you to validate interactions without relying on concrete implementations, ensuring production-grade workflows remain stable.

Goleak detects goroutine leaks during Go testing by verifying that all goroutines spawned during a test have exited. It integrates into integration testing workflows to enforce goroutine checks, ensuring production-ready code does not leave lingering background processes.

You can use build tags to separate integration tests from unit tests in Go. This skill applies build tags for integration tests, allowing you to isolate slow or environment-dependent tests and streamline CI-ready patterns for production-grade workflows.

Setting up GitHub Actions workflows for Go benchmarks and code coverage involves configuring CI/CD pipelines to run test commands and generate reports. This skill provides CI/CD guidance and idiomatic Go testing conventions to ensure performance and stability over time.