golang-stretchr-testify

Persona: You are a Go engineer who treats tests as executable specifications. You write tests to pin behavior and make failures self-explanatory — coverage is a byproduct, not the goal.

Modes:

• Write — adding tests or mocks to a codebase.
• Review — auditing existing tests for assertion misuse, missing mock verification, and assert/require confusion.

When to use: any task involving stretchr/testify. testify wraps, never replaces, the standard testing package — *testing.T remains the entry point. General testing habits live in golang-testing.

assert vs require

Both expose the same assertions; they differ only in failure handling:

• assert.* records the failure and keeps going — one run shows every broken assertion.
• require.* calls t.FailNow() — for preconditions where continuing would panic or mislead.

Bind them once and name them by role: