Currently Browsing

Posts Tagged ‘ graphwalker ’

Graphwalker – Guards and actions

In our previous articles we have already discussed about the finite state machines and about how we can take advantage from this utility of the Graphwalker API. It is based on nodes and vertices which are connected to each other to become a graph and forming a test case to make your job easier and clear.
Moreover Graphwalker provides additional possibilities to make the job be in a batter quality. The edges could be extended by expressions and these can modify the further way of test run. Excluding the label the edge can contain two other elements. The first one called guard and another one is action. These have a unique order like this: Label [Guard] / Action1; Action2;

Graphwalker Path generators and Stop conditions

In this post we will try to give some ideas how to use the Graphwalker Path generators combined with Stop conditions. We recommend you to read our latest post about the Graphwalker API , however here is the snippet of code from last post:

ModelHandler modelHandler = new ModelHandler();
File loginModelFile = new File("'your location for the graphml file'/LoginModel.graphml");
Test testModel = new Test(loginModelFile, true, new A_StarPathGenerator(new EdgeCoverage(1.0)), false);
modelHandler.add("Test", testModel);
modelHandler.execute("Test");
Assert.assertTrue(modelHandler.isAllModelsDone());
String actualResult = modelHandler.getStatistics();
System.out.println(actualResult);
testModel.getDriver().quit();

Graphwalker – how to make *.graphml file to use with Graphwalker API

As we mentioned in “how to start guide” you can generate Java Class from *.graphml file which you created in yEd. First let’s go through the process of making one basic *.graphml file.
Let’s say that we want to make one login smoke test for a random website. The model can be look like the following:

Graphwalker – how to start guide

Graphwalker (http://www.graphwalker.org/) is a state machine based tool, written in Java, generating sequences of tests both for online and offline testing. Diagrams are not UML models (which do not have any functionality) and as a result, much easier to get start with them.
The goal is to create long and unpredictable test sequences. The tool allows to create unique variation of paths across the edges and make these all randomly. The models do not contain any stop or exit points, however stop criteria make it possible to shut them down. In online test cases it makes possible to create the „walking path” during the actual execution. Graphwalker also supports switching between models.