메뉴
Run, debug, and extend tests for Go projects, including generation prerequisites. Use when domain logic, repositories, HTTP handlers, migrations, or unexpected test failures need coverage.
| name | testing-workflows |
| description | Run, debug, and extend tests for Go projects, including generation prerequisites. Use when domain logic, repositories, HTTP handlers, migrations, or unexpected test failures need coverage. |
| license | GNU GPL v3 |
| metadata | {"version":"1.2.0","owner":"mattriley","maturity":"draft","kind":"task"} |
integration-testing-http).code-generation first).database-migrations).make test, go test, or a CI target).make generate before re-running.Use the most specific path for the task; fall through to the debugging sequence when tests fail for unclear reasons. Layer in integration-testing-http when the problem is specifically endpoint contracts, auth behaviour, or request/response assertions over HTTP.
make test # all tests (may run generation first)
make test-unit # unit tests only
make test-integration # integration tests only
go test -v -run TestName ./pkg/... # single test, verbose
Follow this sequence:
make generate, then retry.go test -v -run TestName ./path/to/pkg to isolate.DATABASE_URL is set and migrations are applied.| Layer | What to test |
|---|---|
| Domain / service | Validation rules and business logic (prefer table-driven tests) |
| Repository | Persistence behaviour against a real or in-memory DB |
| HTTP handlers | Status codes, auth enforcement, request/response shapes |
make generate before make test whenever schema, query, or template files changed.code-generation first when failures smell like stale generated inputs rather than test logic.The domain validation test is failing after I renamed a field — isolate it and show me the fix.Add integration tests for the new repository method so it works against both SQLite and Postgres.The CI test run is red but I can't reproduce it locally — step me through the debugging sequence.references/examples.md — concrete user utterances, expected behaviour, and model answer shapesreferences/edge-cases.md — near-miss requests, partial matches, and first-attempt failure patternsUse when auditing JS/TS code health with Fallow - dead code, duplication, boundaries, or cleanup; not for debugging failures.
Use when a JavaScript or TypeScript project needs Knip to find unused dependencies, exports, files, or unresolved imports; not for runtime failures or dormant-task recovery.
Use when creating or revising a reusable agent skill under skills/<name>/SKILL.md — deciding activation, layering, examples, or validation, or choosing between a skill vs. instructions vs. a specialized agent.
Draft structured documents, audit prose readability, and review short audience-facing metadata strings. Use when the primary work is writing, editing, or copy quality.
Use when user wants to write, refactor, or expand documentation (README, guides, API docs, runbooks, specification documents).
Use when creating or updating agent instruction files (AGENTS.md for Pi, copilot-instructions.md for Copilot, per-path guides, or AGENTS.md router) — especially when instruction files are too long, generic, or stale, or when agents repeatedly make the same avoidable mistakes.