go-testing-with-testify

Go Testing With Testify

Workflow for writing, reviewing, and hardening Go tests built on the standard testing package and the stretchr/testify toolkit (assert, require, mock, suite).

Go+testify tests are checks — automated pass/fail assertions on behavior contracts. Testing as investigation — charters, heuristics, oracles under stress, edge-case discovery, perspective rotation — is upstream. Compose with tester-mindset when strategy, risk framing, or the shape of the unknown dominates.

When To Use

• writing new Go unit, integration, or HTTP handler tests with testify
• refactoring existing *_test.go files: tightening assertions, extracting table-driven tests, introducing subtests, or adding t.Parallel()
• reviewing PRs that add or change Go tests
• triaging a flaky Go test (intermittent, -race complaints, order-dependent)
• replacing reflect.DeepEqual / string-match / manual error checking with testify assertions, or deciding when not to
• deciding between a hand-written fake and testify/mock, or between flat subtests and a suite.Suite
• pairing with tester-mindset for claims, oracles, and edge-case coverage
• pairing with backend-guidance or backend-systems-guidance for service- boundary test design in Go services

Not For

• standing up a Go module or repo-level test tooling from scratch — that is a one-off install step (go mod init, go get github.com/stretchr/testify) not a skill-shaped workflow
• strategy work without any testify or testing code in the loop — that is a tester-mindset job
• pure code-style review of non-test Go code — this skill should not be primary; use the repo's implementation or review skill set instead, typically backend-guidance or backend-systems-guidance for Go services
• Ginkgo, Gomega, go-cmp-only, or gocheck suites — the testify idioms below will fight those stacks

Routing Flowchart

digraph route {
    "Main artifact is testify-based Go test code or test review?" [shape=diamond];
    "Main artifact is strategy,\nedge-case discovery, or test planning\nwithout concrete test code?" [shape=diamond];
    "go-testing-with-testify" [shape=box];
    "tester-mindset" [shape=box];
    "coding-guidance-go or another repo skill set" [shape=box];

    "Main artifact is testify-based Go test code or test review?" -> "go-testing-with-testify" [label="yes"];
    "Main artifact is testify-based Go test code or test review?" -> "Main artifact is strategy,\nedge-case discovery, or test planning\nwithout concrete test code?" [label="no"];
    "Main artifact is strategy,\nedge-case discovery, or test planning\nwithout concrete test code?" -> "tester-mindset" [label="yes"];
    "Main artifact is strategy,\nedge-case discovery, or test planning\nwithout concrete test code?" -> "coding-guidance-go or another repo skill set" [label="no"];
}