golang-testing
GoLang testing guidelines
When & Why to Use This Skill
This Claude skill provides standardized guidelines and templates for GoLang testing, specifically focusing on the industry-standard table-driven test pattern. It helps developers improve code quality and maintainability by providing a structured approach to unit testing, ensuring consistent test implementations across Go projects.
Use Cases
- Writing new Go tests: Automatically generate a clean, table-driven test structure for new functions to ensure comprehensive input/output coverage.
- Refactoring legacy tests: Convert verbose or repetitive Go test files into a more readable and maintainable table-driven format.
- Expanding test coverage: Easily add multiple edge cases and boundary conditions to existing tests by simply appending new entries to the test data slice.
| name | golang-testing |
|---|---|
| description | GoLang testing guidelines |
Golang Testing
Instructions
When writing Go tests, always use table-driven test format.
Structure
func TestFunctionName(t *testing.T) {
tests := []struct {
name string
input inputType
expected expectedType
wantErr bool
}{
{
name: "description of test case",
input: inputValue,
expected: expectedValue,
wantErr: false,
},
// additional test cases...
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
// test implementation
})
}
}
When to Use
Apply this format when:
- Writing new Go tests
- Refactoring existing Go tests
- Adding test cases to existing tests