golang-testing

Name: golang-testing
Availability: InStock
Author: samymity

Create Go test suites with table-driven tests, benchmarks, and fuzzing.

1|Updated Mar 3, 2026

Search Tags:#testing #tdd #go #test coverage #benchmarks #table-driven tests #fuzzing

Ready to run

npx skills add https://github.com/samymity/bridge-ventures-backend --skill golang-testing-samymity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: golang-testing
Source: https://github.com/samymity/bridge-ventures-backend/tree/main/.claude/skills/golang-testing
Command: npx skills add https://github.com/samymity/bridge-ventures-backend --skill golang-testing-samymity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create correct, maintainable Go tests that validate behavior early and continuously, reducing bugs and regressions while improving confidence in changes.

Core Features & Use Cases

TDD (RED-GREEN-REFACTOR): Guide test-first development to implement the smallest working behavior, then refactor safely.
Table-driven tests & subtests: Cover many input/output scenarios cleanly with t.Run, including parallel subtests for speed.
Benchmarks, fuzzing, and coverage: Measure performance, discover edge cases automatically, and ensure critical paths stay exercised.

Example: Building a JSON-based config parser where you verify both valid inputs and error paths, then add benchmarks to track performance and fuzzing to harden parsing against unexpected inputs.

Quick Start

Use the golang-testing skill to design a full Go test suite for a new feature, including a TDD-first workflow, table-driven cases, and coverage/bench/fuzz commands for CI.

Frequently Asked Questions about golang-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write table-driven tests with subtests in Go?▼

Table-driven tests in Go use t.Run to execute many input/output scenarios cleanly as subtests, supporting parallel execution for speed. This approach validates behavior across multiple cases while maintaining readable test code.

What is the TDD RED-GREEN-REFACTOR workflow in Go testing?▼

TDD in Go testing guides test-first development to implement the smallest working behavior, then refactor safely. RED writes a failing test, GREEN makes it pass, and REFACTOR improves code without changing behavior, reducing bugs and regressions early.

How do I run Go benchmarks and fuzzing to check performance and edge cases?▼

Go benchmarks and fuzzing measure performance and discover edge cases automatically using go test CLI commands. Fuzzing hardens parsing against unexpected inputs, while benchmarks track performance to ensure critical paths stay exercised during changes.

How do I measure test coverage in a Go project?▼

Test coverage in Go is measured using the go test CLI with the -cover flag, ensuring critical paths stay exercised. Coverage-driven confidence building validates application behavior continuously and identifies untested code in your Go projects.

Can I use this Go testing approach for HTTP handler integration tests?▼

Go testing applies to integration-style HTTP handler tests alongside unit tests, benchmarks, and fuzzing. You can validate application behavior and quality across different test levels using idiomatic patterns like table-driven cases with subtests.