State-machine proof checklist
State-machine proof checklist
Ask:
- Boundary: does the machine own one coherent behavior?
- States: does each state represent a stable mode rather than a temporary flag?
- Events: are timer, sensor, message, reset, and fault events named clearly?
- Guards: are guards side-effect free and testable?
- Actions: are hardware, message, logging, and persistence actions explicit?
- Faults: are timeout, retry, rejection, reset, and service paths covered?
- Coordination: are interactions between machines represented as events?
- Tests: does the test matrix include invalid and wrong-state events, not only the happy path?