Equivalence partitioning
Skill jovd83/test-design-orchestrator/equivalence-partitioning
Transforms requirements and business rules into structured software test artifacts using the right black-box design technique.
npx -y skills add jovd83/test-design-orchestrator --skill equivalence-partitioningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use this skill when Codex needs to derive representative tests from input classes that should behave the same within each valid or invalid partition.
SKILL.md
1.9 KB, as published. Nobody here has run it
Equivalence Partitioning
Read First
./references/equivalence-partitioning.md./references/test-design-shared-conventions.md./assets/templates/partition-table.j2./assets/templates/test-case-table.j2./assets/templates/optimized-test-case-table.j2./assets/templates/coverage-summary.j2
Workflow
- Identify each input dimension that can be divided into behaviorally equivalent classes.
- Define valid and invalid partitions in language the user can audit.
- Choose one representative value per partition unless the user requests deeper sampling.
- Combine valid representatives only when it does not hide which partition is responsible for a failure.
- Keep invalid representatives isolated by default.
Required Output
- partition table with rationale
- representative values
- test case set
- optimized set when valid combinations can be reduced safely
- coverage summary
Guardrails
- Do not collapse partitions that produce meaningfully different system behavior.
- Do not claim equivalence without stating the rule that makes values interchangeable.
- Hand off to BVA instead when the main risk is boundary failure rather than class behavior.