From the model to the test case
In MODICA, the specified behaviour of the system to be tested can be mapped in a usage model. An intuitive modelling grid is used to create a state diagram. Textual requirements can be taken directly from a requirements management tool such as IBM Rational DOORS and linked to the corresponding elements. In addition, it is possible to add further elements such as calculations or descriptions to the model.
>>> Modelling with MODICA
2. Definition of test objectives
Different generation strategies can be defined in order to generate test objectives. They describe the test Content and the scope of the test. Which Targets should be covered exactly, can be adjusted granulary. For example, a strategy should go through all states at least once, a second strategy must cover all requirements, and a third one should test a particular sequence of states (see sequence rules).
>>> Definition of test objectives
3. Generation of test cases
During the test case generation, a test suite is generated for each strategy created in the previous step. Un this test suite all test cases are contained. Together, they meet all objectives of the strategy. Now, all steps of a test case can be viewed and exported. For example into a test automation environment, where test cases are directly executable.
>>> Test case generation
The test cases can be executed both textually, e.g. as HTML, PDF, as well as in test automation systems, e.g. EXAM, MESSINA. In textual export, elements can be also be filtered according requirements. The specific export for automation tool leads to directly executable test cases. On request, it is possible to integrate further tools into the export.
>>> Export and test automation