Go Testing Patterns
Idiomatic Go testing with Muse: table-driven tests, subtests, TDD red-green-refactor, benchmarks, fuzzing, and coverage, with concrete code for each pattern.
- What
- Idiomatic Go testing with Muse: table-driven tests, subtests, TDD red-green-refactor, benchmarks, fuzzing, and coverage, with concrete code for each pattern.
- Cost
- Free
- Needs
- Use "Go Testing Patterns" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a comprehensive Go testing playbook that teaches Muse the idiomatic way to test Go. The TDD workflow is spelled out step by step: write the failing test first, watch it fail, write minimal code, refactor, with a full worked example of a calculator Add function. Table-driven tests get the canonical treatment: a slice of structs with name, inputs, and expected output, run through t.Run subtests, including error-case variants. Subtests, test helpers with t.Helper, and parallel tests are covered. Benchmarks follow with the b.N loop pattern and memory allocation checks. Fuzzing covers the Fuzz target signature, seed corpus, and how to keep failing inputs. Coverage guidance targets meaningful thresholds rather than chasing numbers, plus the race detector for concurrency bugs. Test doubles, table tests for HTTP handlers with httptest, and golden files for complex output round out the set. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: coverage percentages are a signal, not proof of correctness; fuzzing needs a real corpus to find anything. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Go Testing Patterns" with your Muse. Prerequisites: none to install. Pure guidance; a Go project helps. Go toolchain for running tests. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/golang-testing/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Write table-driven tests for [function/package]" or "Add benchmarks for [hot path]." 3. Work through the patterns with Muse: red test first, then minimal code, then refactor. Tip: run go test -race ./... early; the skill treats the race detector as a first-class citizen for anything concurrent. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated tests before trusting them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.