golang-testing
Go testing patterns for unit tests, table-driven tests, subtests, test helpers, mocking/fakes, benchmarks, fuzzing, and coverage. Use when writing or reviewing Go tests to improve correctness, stability, and maintainability.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/golang-testingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package1c303df2…7a3ea5d6
1c303df21fe2…6d8b7a3ea5d69 files · 8.4 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/coding/golang-testing@21cd568
On this page
This skill is about writing tests that are reliable, readable, and useful as documentation.
When to activate
- Writing new tests for functions, packages, or APIs
- Refactoring tests for clarity and reduced flakiness
- Adding benchmarks or fuzz tests
- Stabilizing concurrent or time-dependent tests (
testing/synctest) - Improving coverage without gaming the metric
Core rules (high signal)
- Prefer table-driven tests for coverage and readability.
- Use t.Helper() and t.Cleanup() to keep failures actionable.
- Tests should be deterministic: prefer
testing/synctestovertime.Sleepwhen the code under test usestimeprimitives. - Prefer fakes (in-memory implementations) over heavy mocks.
- Use
t.Parallel()only when the test is truly isolated. - Keep test data local and explicit; avoid hidden cross-test coupling.
- Do not add exported production APIs solely for tests; prefer package seams, interfaces, or local fakes.
- Pair with
test-driven-developmentwhen implementing persistent code or bug fixes test-first. - Pair with
testing-reliabilityfor mock/timing anti-patterns andsystematic-debuggingwhen failure attribution is unclear.
Outcome expectations
- Unit tests are fast, deterministic, and easy to debug.
- Flaky tests are triaged with a repeatable reproduction loop.
- Bench/fuzz/coverage are used as correctness signals, not vanity metrics.
Recommended workflow
- Write/adjust focused unit tests first (table + subtests).
- Run targeted test selection to confirm behavior quickly.
- Add race detector and coverage checks.
- For instability, reproduce with repeated runs (
-count) and isolate state/time dependencies (synctestfortime-based concurrency). - Add benchmarks/fuzz tests when behavior or performance risk justifies them.
Quick checklist for a review
- Setup is outside the assertion loop; minimal shared mutable state
- Subtests have meaningful names (
t.Run("case", ...)) - Error messages show got/want and context
- External dependencies are explicit (DBs, network, time)
- Benchmarks report allocs when relevant (
b.ReportAllocs())
Resources
Load on demand:
references/unit-tests.md— TDD loop, table tests, subtests, parallel subtestsreferences/helpers-fixtures.md— helpers, TempDir, Cleanup, testdata, golden filesreferences/mocking-fakes.md— interfaces for dependencies, fakes vs mocks, examplesreferences/http-testing.md— httptest patterns,NewTestServer(Go 1.27+), JSON assertionsreferences/bench-fuzz.md— benchmarks and fuzzing best practicesreferences/fuzzing-and-race.md— load forgo test -fuzzcampaigns, race detector,goleak,goroutineleakprofiles, andtesting/synctest(Test/Wait/Sleep)references/coverage-ci.md— cover profiles, coverpkg notes, CI integration cautionsreferences/commands.md— go test command recipes (race, timeout, count, patterns)
Files in this version
references/816.6 KB
- bench-fuzz.md1.3 KB
- commands.md974 B
- coverage-ci.md897 B
- fuzzing-and-race.md7.4 KB
- helpers-fixtures.md936 B
- http-testing.md2.1 KB
- mocking-fakes.md1.3 KB
- unit-tests.md1.7 KB
- SKILL.md3.5 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 1c303df2 | Signed | – |
More from AeonDave
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login