A methodology for controlling the size of a test suite
ACM Transactions on Software Engineering and Methodology (TOSEM)
Computer
VIATRA " Visual Automated Transformations for Formal Verification and Validation of UML Models
Proceedings of the 17th IEEE international conference on Automated software engineering
Proceedings of a symposium on Compiler optimization
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Feature-based survey of model transformation approaches
IBM Systems Journal - Model-driven software development
Introduction to Software Testing
Introduction to Software Testing
ATL: A model transformation tool
Science of Computer Programming
Faster and More Focused Control-Flow Analysis for Business Process Models Through SESE Decomposition
ICSOC '07 Proceedings of the 5th international conference on Service-Oriented Computing
Constructing and Visualizing Transformation Chains
ECMDA-FA '08 Proceedings of the 4th European conference on Model Driven Architecture: Foundations and Applications
Detecting and Resolving Process Model Differences in the Absence of a Change Log
BPM '08 Proceedings of the 6th International Conference on Business Process Management
Model transformation testing: the state of the art
Proceedings of the First Workshop on the Analysis of Model Transformations
Hi-index | 0.00 |
For testing model transformations or model transformation chains, a software engineer usually designs a test suite consisting of test cases where each test case consists of one or several models. In order to ensure a high quality of such a test suite, coverage achieved by test cases with regards to the system under test must be systematically measured. Specification-based or code-based coverage can be measured, which leads to the question of how these two approaches are related. In this paper, we investigate the relation between specification- and code-based coverage analysis for model transformation chains and show how such a relation can be established. Based on this, we propose several usage scenarios of such a relation which include identification of code relevant for parts of a given specification and vice versa.