go-testing-strategy

What problem does it solve?

Go services often suffer from inconsistent test coverage, drifting mocks that don't match real wire contracts, unenforced rules for test type placement, and missed checks for concurrency or database atomicity bugs that only surface in production. This skill eliminates these gaps with a clear, enforceable testing strategy tailored to Go service architecture.

Core Features & Use Cases

• Standardized Test Pyramid: Defines exact placement and scope for unit, integration (mocked dependencies), real-infrastructure integration, and end-to-end smoke tests to eliminate redundant or misplaced test effort.
• Contract Safety: Mandates all HTTP mocks validate against JSON Schemas in both directions, preventing silent contract drift that breaks production integrations.
• Workflow Gating: Requires all tests for a spec slice to pass before work advances to the next slice, ensuring acceptance criteria are always verified and no untested code ships.
• Real-Infrastructure Testing: Enforces testing stored procedures, transactional locking, and atomic operations against real Postgres or broker instances instead of mocks that can't catch SQL or concurrency regressions.
• Use Case: For a Go service with external HTTP orchestrators and Postgres stored procedures, this skill ensures you write unit tests for domain logic, schema-validated mocks for the orchestrator, real Postgres tests for stored procedure repositories, and block advancing to the next feature until all tests pass.

Quick Start

Use the go-testing-strategy skill to create a test plan for your new Go service workflow, including unit, integration, and e2e test layers with appropriate gating rules.