Apply Google and Uber Go testing patterns to write and review tests.
npx skills add https://github.com/cxuu/golang-skills --skill go-testing-cxuu
Please help me install this Agent Skill. Skill: go-testing Source: https://github.com/cxuu/golang-skills/tree/main/skills/go-testing Command: npx skills add https://github.com/cxuu/golang-skills --skill go-testing-cxuu
Writing and maintaining high-quality Go tests is challenging without a consistent set of patterns. This skill consolidates Google and Uber style guidance to help teams write clear, reliable tests that are easy to review and extend.
Run go test ./... to execute the test suite and observe results.
High-intent search queries and answers about installing and using this skill.
Table-driven tests and subtests provide the best way to structure Go tests for consistency. Applying patterns from Google and Uber style guides enforces naming conventions and structured layouts, ensuring readability and reliable test outcomes.
To write parallel tests in Go without brittle failures, apply industry-recommended assertion strategies and structured test helpers. Using established patterns minimizes unexpected state sharing and ensures reliable, isolated test execution.
Recommended naming conventions for Go test helpers and subtests align with Google and Uber style guidance. Adopting these specific patterns ensures your test suite remains readable, maintainable, and easy to review and extend over time.
You need to refactor existing Go tests into table-driven patterns when facing duplicated test logic or reduced readability. Refactoring to table-driven tests and subtests consolidates test cases, improving maintainability and minimizing brittle failures.
Yes, this approach to Go testing works without external assertion libraries. It focuses on applying native Go testing patterns, structured test helpers, and assertion strategies defined by Google and Uber style guides to improve test quality directly.
agentclashDetect Go modules and run the test suite after code changes.
mvillmowParse test logs to extract and categorize failures by type.
jonlwowski012Format code across projects using detected configuration files and language-specific formatters.
diegoknskStandardizes .NET testing with xUnit, Moq, SpecFlow, and CI/CD workflows.
