Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/golang-testingEngenharia reversa e 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 instalações+3 em 7 dias39 EstrelasMITsincronizado há 11 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/golang-testing

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
gDiu8+JitJ…TRMFLWBA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote1c303df2…7a3ea5d6
1c303df21fe2…6d8b7a3ea5d69 arquivos · ⁦8.4 KB⁩
VarreduraBaixo1 achado
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding/golang-testing@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em 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)

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd5681c303df2Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login