Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/golang-testingReverse engineering and 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 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-testing

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
gDiu8+JitJ…TRMFLWBA==The CLI checks the SHA-256 and the signature before it writes a file.
Package1c303df2…7a3ea5d6
1c303df21fe2…6d8b7a3ea5d69 files · ⁦8.4 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/coding/golang-testing@21cd568

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)

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd5681c303df2Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login