-
Notifications
You must be signed in to change notification settings - Fork 1
Transformation test case specification
In this case, the source instance model is a pre-prepared instance model, which is transformed by the transformation method under test. It is purpose built for every test case, aiming to trigger the tested functionality.
The target instance model contains the result of the transformation and in each test case it is compared to an expected result. In some cases, the target instance model is prepared to some extent by the test case itself. This is necessary during mapping test cases, as the effects (or lack of them) of other transformation mappings could affect the test results.
Model-to-model transformations consist of numerous transformation mappings. These mapping define, that a certain typed element(s) in the source model should be transformed to a given target model element(s).
As stated previously, model transformations are basically a set of mappings between source and target model elements. Transformation mapping tests check if the transformation implements these mapping according to its specification. Mapping tests can be loosely regarded as unit tests for model transformations.
Similar to regular software testing, integration tests also play an important role in the field of testing model transformations as well. These integration test specify more complex source and expected target models, which cover the functionality of multiple mappings
The main idea behind this page is that if the individual test case specifications follow a predefined formula, the test specification deliverable can be created from individual test case specifications. In this case, these test specifications are JavaDoc header comments that consist of the following sections.
In this section the following should be specified in a short, textual form.
- Type of the test (mapping/integration)
- Short description of the functionality to be tested
- How does the source model trigger this functionality
In this section the structure of the source instance model is specified. It can be done in either textual or a better structured form, for example a tree. In case of complex source models, (typical for integration tests) only the parts of the model which bare actual relevance of the test case should be specified.
This section specifies that to what extent should the target model be prepared by the test case, to avoid unnecessary dependency on certain untested functions.
Finally, the expected target model should also be specified. Similar to the case mentioned before, if complex models are involved, only the relevant parts of the model should be specified.
The projects below should provide an example for the application of the aforementioned test case specification template