How to Create Test Cases Using State-Transition Diagrams?

March 01 11:03 2016 by Nataliia Vasylyna Print This Article

State-transition diagrams are not widely used by the specialists of software testing company. But for certain, they simplify the execution of web application testing and mobile testing. Moreover, diagrams also accelerate the testing procedure.

State-transition diagrams demonstrate the peculiarities of system functionality in a form of notation. As a result, it is easier for testers to create test cases needed to perform functional testing.

If a tester uses state-transition diagram to create test cases, he will cover several levels of system functionality. There are four such levels.

4 Levels of Test Case Coverage:

1. A set of test cases which will ‘visit’ all system states should be created.
2. A tester should design test cases which will trigger all events. Sometimes tests can be the same to check the state of system and happened event.
3. All possible paths should be covered by a set of test cases. But if a diagram has a loop, then it is impossible to define the number of available paths.
4. A tester should write test cases which will check all transitions. It is recommended to perform software testing at this particular level.

Besides diagrams, the state-transition tables can be used during test case creation. One should remember that state-transition diagram and table are not used if the system does not change the state and does not respond to outside event.

Learn more from QATestLab

Testing
Services

Solutions
by Industry

Related Posts:

• 3 Pieces of Advice While Creating Test Cases
• Why Test Cases Should Be Designed?
• How to Begin Writing Test Cases?