Model-Based Testing Tool
The plan is to release the final report at the 2014 UCCAT meeting in September.
If you have evaluated, used, or are using any model-based testing approach, please take a few minutes to respond to the 2014 Model-based Testing User Survey.
The 2014 survey is a collaboration of Dr. Anne Kramer (sepp.med), Bruno Legeard (Smartesting), and Robert Binder (System Verification Associates). It is a follow up to the 2012 MBT User Survey http://robertvbinder.com/real-users-of-model-based-testing/ and includes questions from a survey distributed at last year’s User Conference on Advanced Automated Testing (UCAAT 2013).
Get in touch with other users on IRC. Use freenode.net, channel #graphwalker. There's a webclient.
The main features of GraphWalker are:
No UMLGraphWalker'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 pointsThe 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.
OnlineGraphWalker 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.
Jump between modelsGraphWalker supports switching models when traversing them. This enables re-usage of models and implemented code. See model switching article.