4.5 State Transition Testing

Core Idea

State transition testing is a black-box technique for systems whose behavior depends on state. A state is a condition or mode of the system. An event triggers a possible movement from one state to another. That movement is a transition.

The same event can be valid in one state and invalid in another. For example, submitting a password may be valid while an account is Active, but rejected while the account is Locked.

A state model often includes states, events, transitions, guards, and actions. A guard is a condition that must be true for the transition to occur. An action is the result produced during the transition.

Worked Example: Account Login

Requirement: A user account can be Active, Locked, or Password Reset Required. Three consecutive failed login attempts lock the account. A successful login from Active opens the session. A password reset request moves the account to Password Reset Required. Completing the reset returns the account to Active.

Simplified transitions:

Each transition can be a coverage item. Tests should include normal transitions and invalid or blocked transitions. The invalid transition from Locked plus Try login is important because it confirms the system does not accidentally allow access.

Test Cases from the Model

A transition coverage suite could include:

1. Active plus successful login opens a session.
2. Active plus one failed login stays Active and increments the count.
3. Active plus third failed login moves to Locked.
4. Locked plus login attempt stays Locked and rejects access.
5. Locked plus admin unlock returns to Active.
6. Active plus reset request moves to Password Reset Required.
7. Password Reset Required plus normal login stays in reset-required state.
8. Password Reset Required plus complete reset returns to Active.

A stronger suite may also cover transition sequences. For example: Active, failed login, failed login, failed login, Locked, admin unlock, Active. Sequence tests catch defects that appear only after history accumulates.

Coverage Measurement

Transition coverage is calculated as:

covered transitions / total transitions * 100

If the model has 8 transitions and tests cover 7, transition coverage is 87.5 percent. If the missing transition is Locked plus Try login, the report should highlight it because security-sensitive invalid transitions can be high risk.

Some projects measure state coverage instead. State coverage counts whether each state was reached at least once. State coverage is weaker than transition coverage because reaching a state does not prove all important events from that state were tested.

When to Use It

Use state transition testing for login flows, shopping carts, order lifecycles, subscriptions, payment authorization, device modes, file upload processing, workflow approvals, network protocols, and embedded systems.

It is less useful when the behavior is stateless. A simple tax rate lookup by income range may be better tested with EP, BVA, or decision tables.

Exam Strategy

When an exam question describes states and events, draw a small table or diagram. Ask: what state am I in, what event happens, what state should follow, and what action is expected?

Watch for tests that try an event in the wrong state. Those are not automatically useless. Invalid transitions are often deliberate tests of robustness, security, and workflow control.