jovd83 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.