i. Graph Based Testing is also called as State Based Testing

ii. It provides a framework for model based testing.

iii. Black-box methods based on the nature of the relationships (links) among the program objects (nodes), test cases are designed to traverse the entire graph.

iv. Transaction flow testing – nodes represent steps in some transaction and links represent logical connections between steps that need to be validated.

v. Finite state modeling – nodes represent user observable states of the software and links represent transitions between states.

vi. Data flow modeling – nodes are data objects and links are transformations from one data object to another.

vii. Timing modeling – nodes are program objects and links are sequential connections between these objects, link weights are required execution times.

Steps in graph testing:

i. Build a graph model.

ii. Identify the test requirements.

iii. Select test paths to cover those requirements.

In order to design test design cases following steps are used:

i. Understanding the system

ii. Identifying states, inputs and guards.

iii. Create a state graph model of the application.

iv. Verify whether State graph that we modeled is correct in all details.

v. Generate sequence of test actions.

Derive test data so that those test paths can be executed.

Example: