القائمة
Run and extend the end-to-end HTTP integration tests (SQLite in-memory) for mjr.wtf, covering auth, create/list/delete, redirects, and analytics. Use when changing handlers, middleware, or API contracts.
| name | integration-testing-http |
| description | Run and extend the end-to-end HTTP integration tests (SQLite in-memory) for mjr.wtf, covering auth, create/list/delete, redirects, and analytics. Use when changing handlers, middleware, or API contracts. |
| license | MIT |
| compatibility | Requires Go, make, and generated code. |
| metadata | {"repo":"mjrwtf","runner":"github-copilot-cli","version":1.1} |
| allowed-tools | Bash(git:*) Bash(make:*) Bash(go:*) Read |
make targets when available; fall back to direct CLI commands when needed.make test-integration
Targeted runs:
go test -v -run TestE2E ./internal/infrastructure/http/server/
go test -v -run TestAPI ./internal/infrastructure/http/server/
openapi.yaml) and validate it.See docs-site/src/content/docs/operations/integration-testing.md for the current suite structure and scenarios.
Run mjr.wtf locally using Docker Compose (SQLite), including migrations, logs, and teardown.
Operate and validate mjr.wtf observability endpoints (/health, /metrics) and logging-related behavior. Use when adding metrics, changing auth around metrics, or debugging production-like issues.
Apply project-specific security and privacy guardrails (auth, headers, rate limiting, logging). Use when touching authentication, request handling, metrics exposure, or anything that could leak sensitive data.
Run, debug, and structure tests for this Go project (unit + integration), including generation prerequisites. Use when changing domain logic, repositories, HTTP handlers, or migrations.
Run and troubleshoot project code generation (sqlc + templ).
Configure mjr.wtf safely via environment variables and .env files.