eng-test-conventions
FeaturedGo test-shape discipline for Compozy. Use when writing or editing *_test.go under cmd or internal after test placement is justified. Do not use for non-Go tests, fixture-only changes, or as a replacement for eng-consolidate-test-suites.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- compozy
- Repository
- compozy/compozy
- Created
- 7 months ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
eng-consolidate-test-suites
Use when adding, moving, reviewing, or auditing tests in Compozy to identify the invariant, owning layer, and canonical suite before changing coverage. Do not use as a replacement for framework-specific testing skills or final verification gates.
eng-code-guidelines
Go production discipline for Compozy. Use when writing or editing non-test Go files under cmd or internal, including config, logging, CLI, concurrency, and process-lifecycle paths. Do not use for Go tests; pair it with the narrower schema, contract, or cleanup skill when those domains apply.
go-tests
Go testing conventions that follow established industry standards: the Go wiki's Test Comments, the test sections of the Google Go Style Guide, and the testing package. Covers where tests live, naming, useful failure messages (got before want, function and input named), cmp diffs, t.Error vs t.Fatal, table-driven tests and subtests, test helpers, fakes and real transports, examples, benchmarks, fuzz tests, and what to avoid (assertion libraries, sleeps, shared global state). TRIGGER when: writing, editing, or reviewing Go test code (_test.go files). DO NOT TRIGGER when: working in a non-Go language, or only on production code.