jovd83 State Transition
Read First
./references/state-transition.md./references/test-design-shared-conventions.md./assets/templates/state-table.j2./assets/templates/state-transition-table.j2./assets/templates/test-case-list.j2
Workflow
- Identify states, events, guards, and resulting actions.
- Confirm the start state and invalid-transition behavior when the requirement does not make them obvious.
- Build a transition model before writing tests.
- Select the coverage target: all states, all transitions, or switch coverage.
- Include invalid-transition tests when the system rejects illegal events explicitly.
Required Output
- state inventory
- transition model
- path set for the requested coverage level
- negative-transition scenarios when supported
- traceable test list
Guardrails
- Do not use state-transition testing when the requirement is really just a rule matrix or a simple range check.
- Do not invent hidden states to make the model look complete.
- Separate valid transitions from inferred invalid ones.