Define test pyramid placement and gating rules for Go services.
npx skills add https://github.com/trypanic/skills --skill go-testing-strategy
Please help me install this Agent Skill. Skill: go-testing-strategy Source: https://github.com/trypanic/skills/tree/main/go-testing-strategy Command: npx skills add https://github.com/trypanic/skills --skill go-testing-strategy
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.
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.
High-intent search queries and answers about installing and using this skill.
A Go testing strategy should use a standardized test pyramid to define exact placement for unit, integration, real-infrastructure, and end-to-end tests. This eliminates redundant effort by enforcing scope rules for domain logic, mocked HTTP clients, and real Postgres stored procedure tests.
To prevent HTTP mock contract drift in Go integration testing, you should mandate that all HTTP mocks validate against JSON Schemas in both directions. This ensures mocked dependencies match real wire contracts and prevents silent integration failures.
To test stored procedures and database atomicity in Go, you should enforce real-infrastructure integration testing against actual Postgres instances. This approach catches SQL regressions, transactional locking issues, and concurrency bugs that mocked databases cannot detect.
You can enforce workflow gates by requiring all tests for a spec-driven feature slice to pass before work advances to the next slice. This gating mechanism ensures acceptance criteria are always verified and no untested Go service code ships.
The best way to handle race-safe concurrency testing patterns in Go services is to implement standardized test strategies that enforce real-infrastructure testing. This validates atomic operations and transactional locking against real brokers or Postgres instances to catch concurrency regressions.
Yes, this Go testing strategy applies directly to spec-driven feature slices by applying workflow gating rules. It ensures all unit, integration, and end-to-end tests for a slice pass before advancing, verifying acceptance criteria across HTTP orchestrators and repositories.
FernanSuozaDesign API and event contracts with OpenAPI and JSON Schema specifications.
dixusExecute automated smoke tests against a running Docker stack.
inakamGenerates Gaphic-driven Gaphic tests for Python and Java projects.
marquesfelipCodify backend testing strategies using the test pyramid across unit, integration, and end-to-end tests.
