Artifact content
Public sample: Google Drive .drawio file
This artifact demonstrates State Transition Testing using an article lifecycle model. The diagram makes states and allowed transitions explicit instead of leaving workflow logic implicit.
- States covered: Start, Draft, On Review, Published, Rejected, Deleted
- Transitions covered: Mark as Draft, Submit on review, Approve, Reject, Make changes, Edit, Delete article, Delete
- Testing value: the model helps identify valid transitions, invalid transitions, return paths, and states that require specific entry or exit conditions
This is useful because state-based features often fail not in isolated fields, but in the logic between statuses. A state transition model helps design tests for what is allowed, what is forbidden, and what should happen after a status change.
Together with the artifacts for Equivalence Partitioning, Boundary Value Analysis, Pairwise Testing, and Decision Table Testing, this closes another important test-design technique with a concrete public example.