testing-workflows

Tooling assumptions

• Use a terminal runner with bash and git available.
• Prefer make targets when available; fall back to direct CLI commands when needed.

Fast paths

• All tests (runs generation first):

make test

• Unit tests only:

make test-unit

• Integration tests only (HTTP server suite):

make test-integration

Debugging failures

1. If you see compile errors for generated packages, run:

make generate

2. Re-run the failing package with verbose output:

go test -v ./path/to/pkg

3. If the failure is DB-related, confirm DATABASE_URL is correct and migrations are applied (for integration setups).

What to cover when adding features

• Domain validation (table-driven tests).
• Repository behavior (in-memory SQLite tests).
• HTTP behavior (status codes + auth + schemas).