Design Testing Strategy
Use before writing any type of tests.
Install
npx skills add NeoLabHQ/context-engineering-kit --skill design-testing-strategy -g -a claude-code -y- Repository
- NeoLabHQ/context-engineering-kit1.8k
- Category
- Testing
- Updated
- 2mo ago
- License
- GPL-3.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use before writing any type of tests. Distills 14 industry sources into deterministic decision gates, schemas, and worked test examples.
Design Testing Strategy
A reference manual for designing a fit-for-purpose, fit-for-criticality testing strategy.
This skill is decision-oriented, not philosophical: every gate is deterministic (ON when X / OFF when Y), every schema is enforced (field ordering matters), every example is worked end-to-end.
How To Use This Skill
- Read Decision Gates in order (Gate 0 -> Gate 6). Each gate is independent, you may finish with any subset of test types ON.
- Apply Strategic Skip Heuristics to remove ON gates that would yield low ROI for this artifact.
- For each ON gate, fill the Test Matrix Schema (
selected_typesentry), the field order is load-bearing. - List rejected types in
rejected_typesand deliberate skips indeliberately_skipped. - Produce a Test Cases to Cover markdown bullet list using ISTQB techniques from Case Design Techniques.
- Cross-check against the matching Worked Example (A pure function / B HTTP+DB endpoint / C UI component).
Decision Gates
Apply gates in numeric order. Each gate produces an independent boolean (applies: true|false). Gates do NOT veto each other, a single artifact may have unit + integration + contract + property-based all ON.
