GraphWalker is a Model-Based Testing tool. It parses models [finite-state machines] which are designed using the yEd, http://www.yworks.com/en/products_yed_about.html, and generates test sequences. The tool generates offline and more importanly, online test sequences from Finite State Machines and Extended Finite State Machines. See also: http://graphwalker.org
The main features of GraphWalker are:
GraphWalker's own ruleset in conjunction with GraphML, is easier to get started with than UML. As testers, we do not need all functionality that UML has to offer.
###No exit/stop points ###
The idea behind this, is that we want long, unpredictable test sequences. We do not want to walk the same path every time we execute a test. We want variation, spiced with randomness. This will create a better 'test coverage' of the system under test. The way to tell GraphWalker to stop generating test sequences are done by means of Stop Criterias, passed as arguments to the tool.
It supports online test sequence generation. Using the online mode, the tool is capable of testing non-deterministic systems. In essence, this means that the path walked through the model is decided runtime, during the actual test execution. This is very helpful if your test execution tool needs to communicate with the model during the test.
GraphWalker supports the possibility to switch model caused by an event. For example, let's say we have a model that executes the navigation of the GUI of a mobile phone. At any point in that execution, an incoming call will be such an event that will switch from navigating the GUI, to a model that handles the call.
https://github.com/KristianKarl/GraphWalker/issues
No code changes only the project structure has been transformed into a multi-module maven project.
handles dependencies and plugins versioning, also gives all inheriting modules basic functionality like different kind of report generation.
contains the GraphWalker code, this module can later on be split up into several modules eg. gui and webservice modules.
builds the executable standalone jar file, the reason for this being done in a separate module is due to the fact that each maven project only should have one build artifact.
Run "mvn clean install", in each module to compile and install the artifact generated by the module in the local repository, add -Dmaven.test.skip to omit the tests. This is true for all modules except graphwalker-parent, who will instead build the entire project.
mvn test