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 instalaciones+3 en 7 días39 EstrellasMITsincronizado hace 11 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/golang-testingEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete1c303df2…7a3ea5d6
1c303df21fe2…6d8b7a3ea5d69 archivos · 8.4 KBEscaneoBajo1 hallazgo
- Enlaces a dominios externos
Fuentegithub.com/AeonDave/malskill/tree/main/coding/golang-testing@21cd568
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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)
Archivos de esta versión
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
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 1c303df2 | Firmada | – |
Más de AeonDave
Todo de este publicadorMás en Ingeniería inversa y fuzzing
Ver la categoríaPregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login