golang-testing

Topics in the source

• Go Testing Patterns
• When to Activate
• TDD Workflow for Go
• The RED-GREEN-REFACTOR Cycle
• Step-by-Step TDD in Go
• Table-Driven Tests
• Table-Driven Tests with Error Cases
• Subtests and Sub-benchmarks

Comprehensive Go testing patterns for writing reliable, maintainable tests following TDD methodology. 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 The standard pattern for Go tests. Enables comprehensive coverage with minimal code. Testing against expected output files stored in testdata/. | Code Type | Target | |-----------|--------| | Critical business logic | 100% | | Public APIs | 90%+ | | General code | 80%+ | | Generated code | Exclude | DO: 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 DON'T: 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 Remember: Tests are documentation. They show how your code is meant to be

This is an excerpt. Refer to the complete source and its current requirements.