# Testing Go Code

> Run Go unit tests, coverage reports, and benchmarks. Use when you need to run tests, check coverage, run benchmarks, or regenerate mocks after interface changes.

- Skill: `mrpointer/testing-go-code` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mrpointer/testing-go-code`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mrpointer/testing-go-code/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mrpointer (https://skillmd.com/u/mrpointer)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mrpointer/testing-go-code

---


# Testing Go Code

All commands run from the Go module root (`cova/`).

## Unit Tests

```bash
task test                       # Run all tests with race detection
task test -- -run TestName      # Run specific test(s)
task test -- -short             # Skip integration tests
```

For test conventions (naming, assertions, table-driven patterns, mock usage), see the `writing-go-tests` skill.

## Coverage

```bash
task cov
```

Runs tests with coverage and opens an HTML report in the browser.

## Benchmarks

```bash
task bench
```

Runs all benchmarks with memory allocation stats.

## Combined Check

```bash
task check
```

Runs tests + lint in sequence. Use before committing.

## Mock Regeneration

```bash
mockery
```

Run from the module root with no arguments after adding or modifying interfaces. Configuration is in `.mockery.yml`.

**NEVER edit generated mock files (`*_mock.go`) manually.** Always regenerate with `mockery`. This applies to all mock changes — adding parameters, renaming methods, updating signatures, fixing imports. No exceptions.

### When `mockery` fails due to stale mocks

Stale mock files frequently cause `mockery` to fail (e.g., type conflicts from old signatures). When this happens:

1. Delete the stale `*_mock.go` file(s)
2. Re-run `mockery`

Do NOT attempt to fix the mock file by hand — delete and regenerate.