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 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/golang-testingScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto1c303df2…7a3ea5d6
1c303df21fe2…6d8b7a3ea5d69 file · 8.4 KBScansioneBasso1 segnalazione
- Link a domini esterni
Sorgentegithub.com/AeonDave/malskill/tree/main/coding/golang-testing@21cd568
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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)
File di questa versione
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
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 1c303df2 | Firmata | – |
Altro da AeonDave
Tutto da questo editoreAltro in Reverse engineering e fuzzing
Vai alla categoriaChiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login