Download Pilot Project for Model Based Testing using Conformiq Qtronic

7.4 Lessons learned
In addition to the results mentioned in section 7.1, the pilot project also resulted in a
list of general guidelines to keep in mind when working with Conformiq Qtronic and
MBT in general.
Modelling
 Model in small increments and generate test cases often to find errors
and time consuming functions in the model earlier.
 Don't try to model several scenarios at once. Keep it simple between
iterations to locate errors faster.
 Specify interfaces and signals (records) first, then describe the
behaviour.
 Use the requirement keyword frequently in the model. Requirement
coverage is the best way to assure correct functionality.
 Use the require keyword to set or limit variables, and the assert
keyword to find errors.
 Use the complete and incomplete keywords to control the test cases, or
check the Only finalized runs option in the preferences.
 Avoid using the Modeler as a coding tool; call on functions from the
Modeler, but write the functions in the textual parts.
Test case generation
 Keep in mind that long generation times are often necessary when
dealing with complex models, and do not always point to a badly
designed model.
 Keep old test cases before regenerating a new test suite to reduce
generation time (provided that the new test suite matches part of, or
the whole of, the previous test suite).
Scripting
 Use the built-in functions and the ValueVisitor. They are efficient and
help keep the implementation of the scripter simple.
 Don't do everything at once. Start with general text output before
syntax to avoid unnecessary mistakes.
59 (67)