// Free testing tool

State Transition
Testing Tool

Map the states and events in a system, then get a diagram, a state table and the tests to cover every transition, valid and invalid.

// Tool

Build Your State Transition Tests

List the transitions, then get the diagram, the state table and every test.

From state Event To state Action (optional)
State transition diagram

The highlighted state is the start. Dashed states can't be reached from the start.

State table

Each cell shows the state the event moves to. A dash (–) marks an invalid transition, where that event shouldn't change the state.

Tests

Things to know

  • Every test starts from the start state. The "Get to the starting state" column lists the events to send first, using the shortest route.
  • Invalid transitions are expected to be rejected or ignored, leaving the state unchanged. Check the requirements for exactly what should happen, such as which error message appears.
  • These tests check each transition once on its own. Defects that only appear after a particular sequence, such as two failed logins followed by a password reset, need longer tests.
// FAQs

Frequently Asked Questions

It's another name for testing every valid transition at least once, which is what the valid tests in this tool do. 1-switch coverage tests every pair of transitions in a row, such as a failed login followed by a successful one. It catches more defects but needs many more tests.

Because the system should stay where it is, and sometimes it doesn't. A locked account that accepts the right password, or a delivered order that can still be cancelled, are both defects that only invalid transition tests would catch.

Either a transition is missing from the list, or the requirements describe a state the system never actually gets into. Both are worth raising before testing starts.

A decision table looks at combinations of conditions at one moment. State transition testing looks at what happens over time, where the order of events matters. Many systems need both, such as a login that checks several conditions and also locks after repeated failures.

No. The states and events come from the requirements, or from how the system behaves when you use it.

All free testing tools →