You are here

GraphWalker

Modeling GUI structures with GraphWalker

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

When modeling for a GUI of a system. It can be hard to find the best way for representing the modeled behavior on the system.

One have to think about haw to model what the tests interacts with. For bigger structures there are several approaches. Here are two approached, which are
frequently applied.

Modeling for GraphWalker 201

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

JavaScript Enabled Modeling

I have played a little around with GraphWalker and JavaScript enabled models for ESFM. The “-j” option

[-j]

Enable JavaScript engine

java -jar graphwalker-2.6.3.jar offline -f MBT201.graphml -g RANDOM -s REACHED_VERTEX:End -j > output.txt –x

Output:

Start

Modeling 101 for GraphWalker

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

Here under some examples on hos to model different “code” structures.

The following examples are without any Graphwalker related constraints. This is only intended for showing how to model the structures. So no Guards,
weights and javascript enabled in these model exambles.

Model Based Testing with GraphWalker 2

I wrote prior to the release of GraphWalker 3. So keep in mind the not all information in this article is valid for GW3. I'll make an updated version soon.

Model-based testing is a new and evolving technique for generating a suite of test cases from requirements.

Testers using this approach concentrate on a data model and generation infrastructure instead of hand-crafting individual tests.

Model-based testing depends on three key technologies:

Ending a test in Model Based Testing with GraphWalker

When modeling is might not always be the best implementation of the model to force all the test to end in the same state. (But is it more manageable to model with this thought in mind.)
Sometime the test need to stop when a specific condition arises.
A stop-condition, is a stop criteria for a given generator. It will halt the generation of a test sequence when the given criteria is reached.
GraphWalker support the following stop conditions.

yED - Free Modeling Tool

yEd is a powerful diagram editor that can be used to quickly create diagrams manually or import external data for analysis and auto-magically arrange even large data sets by just pressing a button. You can use yEd to quickly create flow charts, BPMN and UML diagrams, organization charts, mind maps, and many other kinds of diagrams, graphs, and networks. Choose from a wide range of highly sophisticated layout algorithms to automatically arrange diagrams in no time. An intuitive and visually appealing user interface makes creating diagrams fun.

GraphWalker - Open Source Model Based Testing

GraphWalker is a tool for generating offline and online test sequences from Finite State Machines and Extended Finite State Machines. GraphWalker is only the tool for traversing your models. It does not have a GUI to modeling it self. However, it is normal to "bundle" GraphWalker with the free graphml editor yED. yED provides a free and nice tool for creating and editing models fit for GraphWalker.