jovd83 Decision Table
Read First
./references/decision-table.md./references/test-design-shared-conventions.md./assets/templates/decision-table.j2./assets/templates/optimized-decision-table.j2./assets/templates/test-case-table.j2
Workflow
- Extract conditions and resulting actions.
- Distinguish stated rules from unstated combinations.
- Build the full rule space only as far as the requirement supports it.
- Mark impossible or unspecified combinations explicitly.
- Optimize only when multiple columns truly produce the same outcome and the same oracle.
- Derive one scenario per retained rule column.
Required Output
- condition list
- action list
- full or partially constrained decision table
- optimized decision table when valid
- scenario list tied back to retained rules
Guardrails
- Do not invent policy for unspecified combinations.
- Do not use "don't care" to hide a meaningful rule difference.
- Prefer a coverage gap note over a fake complete matrix.