Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
aeondave/golang-testingIngeniería inversa y fuzzing

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-testing

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
gDiu8+JitJ…TRMFLWBA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete1c303df2…7a3ea5d6
1c303df21fe2…6d8b7a3ea5d69 archivos · ⁦8.4 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
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.

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/synctest over time.Sleep when the code under test uses time primitives.
  • 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-development when implementing persistent code or bug fixes test-first.
  • Pair with testing-reliability for mock/timing anti-patterns and systematic-debugging when 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.

  1. Write/adjust focused unit tests first (table + subtests).
  2. Run targeted test selection to confirm behavior quickly.
  3. Add race detector and coverage checks.
  4. For instability, reproduce with repeated runs (-count) and isolate state/time dependencies (synctest for time-based concurrency).
  5. 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 subtests
  • references/helpers-fixtures.md — helpers, TempDir, Cleanup, testdata, golden files
  • references/mocking-fakes.md — interfaces for dependencies, fakes vs mocks, examples
  • references/http-testing.md — httptest patterns, NewTestServer (Go 1.27+), JSON assertions
  • references/bench-fuzz.md — benchmarks and fuzzing best practices
  • references/fuzzing-and-race.md — load for go test -fuzz campaigns, race detector, goleak, goroutineleak profiles, and testing/synctest (Test/Wait/Sleep)
  • references/coverage-ci.md — cover profiles, coverpkg notes, CI integration cautions
  • references/commands.md — go test command recipes (race, timeout, count, patterns)

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.11.13-21cd56813 nov 202621cd5681c303df2Firmada–

Pregunta 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. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login