golang-testing
Provides a comprehensive guide for writing production-ready Golang tests. Covers table-driven tests, test suites with testify, mocks, unit tests, integration tests, benchmarks, code coverage, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, memory leaks, CI with GitHub Actions, and idiomatic naming conventions. Use this whenever writing tests, asking about testing patterns or setting up CI for Go projects. Essential for ANY test-related conversation in Go.
83
86%
Does it follow best practices?
Impact
69%
1.53xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
64%
36%Add Test Coverage for a Payment Processing Package
gotests scaffolding and enrichment
gotests invocation
0%
0%
External test package
0%
0%
Named subtests
30%
100%
t.Parallel in subtests
0%
100%
Top-level t.Parallel
0%
100%
Example functions
0%
100%
Example Output comments
0%
0%
Naming conventions
83%
100%
Error path coverage
100%
100%
Edge case coverage
100%
100%
Testify as helper
0%
0%
100%
28%Set Up Integration Tests for a Blog Post Repository
Integration test fixture layout
Integration build tag
100%
100%
No testing.Short() separation
100%
100%
testdata directory location
100%
100%
Docker Compose fixture
100%
100%
Schema SQL fixture
100%
100%
embed.FS for fixtures
100%
100%
testify/suite embedding
0%
100%
SetupSuite lifecycle
37%
100%
Per-test isolation
50%
100%
TearDownSuite
50%
100%
Suite runner function
0%
100%
Test independence
100%
100%
45%
10%Write Tests for a Token Bucket Rate Limiter
Concurrent code time mocking and goroutine leak detection
No time.Sleep in tests
0%
0%
clockwork or synctest used
0%
0%
goleak imported
0%
100%
goleak in TestMain or per-test
0%
100%
Shutdown goroutine cleanup test
50%
100%
Refill behavior tested
100%
50%
Named subtests
0%
0%
t.Parallel usage
0%
0%
Fake clock via Clock interface
100%
0%
Token exhaustion tested
100%
100%
- Repository
- samber/cc-skills-golang
- Commit
b88f91d
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.