golang-testing

Comprehensive Go testing patterns for writing reliable, maintainable tests following TDD methodology. The standard pattern for Go tests. Enables comprehensive coverage with minimal code. Testing against expected output files stored in testdata/ . DO: DON'T: Remember : Tests are documentation. They show how your code is meant to be used. Write them clearly and keep them up to date. - Writing new Go functions or methods - Adding test coverage to existing code - Creating benchmarks for performance-critical code - Implementing fuzz tests for input validation - Following TDD workflow in Go projects - Write tests FIRST (TDD) - Use table-driven tests for comprehensive coverage - Test behavior, not implementation - Use t.Helper() in helper functions - Use t.Parallel() for independent tests - Clean up resources with t.Cleanup() - Use meaningful test names that describe the scenario - Test private functions directly (test through public API) - Use time.Sleep() in tests (use channels or conditions) - Ignore flaky tests (fix or remove them) - Mock everything (prefer integration tests when possible) - Skip error path testing