LEARN. PRACTICE. GROW.Concept and mechanism
A request may move from draft to submitted and then approved or rejected. Testing each transition separately does not necessarily demonstrate that adjacent sequences work. Single-transition coverage, also called zero-switch, observes each valid edge; one-switch requires adjacent valid pairs. For draft to submitted to approved, the two transitions in the same sequence matter. Include guards and actions in the model: approval authorization may depend on an identity different from the submitter. An invalid event can be a relevant rejection test even when it does not count toward valid-transition coverage. Do not infer sequence coverage from a count of visited states.
Guided application
A CRUD matrix connects create, read, update, and delete operations with entities and functions. In one example, one module changes a preference and another reads it; testing both separately with preloaded data may miss a stale read. Execute the sequence on the same artificial entity and confirm the agreed consistency rule. Missing delete coverage in the matrix is a question to investigate, not permission to add a feature contradicting product policy. Combine these models with user journeys: main path, alternatives, and recovery after error. Sequence-generation tools can help, but depend on a correct model and checks distinguishing expected from observed outcomes.
Create and update in module A, read in B, using the same entity.
Common pitfalls
States treated as transitions; isolated operations treated as sequence; CRUD treated as mandatory deletion.
Related topics: Analysis and evidence in the test process · Priority and residual risk · Domains, boundaries, and combinations
Model actions, guards, and data continuity.
Reference: Hypothesis stateful testing · CTAL-TA v4.0 (2025)