What problem does it solve? Testing Go Gin APIs requires coordinating many patterns — httptest recorders, mocked repositories, table-driven subtests, testcontainers for real databases, and CI pipelines — and developers often end up with shallow handler tests that miss error paths, race conditions, and SQL correctness issues. ## Core Features & Use Cases - Unit Testing Patterns: Handler tests with httptest and mock services, service tests with mocked repositories, table-driven validation tests, fixtures, middleware isolation tests, benchmarks, fuzz tests, and golden file snapshots. - Integration & E2E Testing: TestMain lifecycle with testcontainers PostgreSQL, truncate/rollback cleanup, migration up/down tests, fixture loading, and full register→login→CRUD flows. - Load Testing & CI: Go benchmarks, Vegeta and k6 scripts with latency thresholds, benchstat regression detection, and a three-job GitHub Actions pipeline with an 80% coverage gate. - Use Case: You just built a UserHandler with JWT-protected routes. Use this Skill to generate table-driven validation tests, service tests asserting typed AppError codes with errors.As, and an integration suite that verifies duplicate-email constraints against a real Postgres container. ## Quick Start Ask the AI to write table-driven unit tests for your Gin handler and an integration test for the repository using testcontainers.