Architectural structures and views
ISAW '98 Proceedings of the third international workshop on Software architecture
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Third eye — specification-based analysis of software execution traces (poster session)
Proceedings of the 22nd international conference on Software engineering
ECOOP '99 Proceedings of the 13th European Conference on Object-Oriented Programming
Automating Formal Specification-Based Testing
TAPSOFT '97 Proceedings of the 7th International Joint Conference CAAP/FASE on Theory and Practice of Software Development
Tracing Execution of Software for Design Coverage
Proceedings of the 16th IEEE international conference on Automated software engineering
Tracing Execution of Software for Design Coverage
Proceedings of the 16th IEEE international conference on Automated software engineering
Tracing the Application of Clinical Guidelines
Advanced Web and NetworkTechnologies, and Applications
Hi-index | 0.00 |
Test suites are designed to validate the operation of asystem against requirements. One important aspect of atest suite design is to ensure that system operation logicis tested completely. This is a difficult task. Codecoverage tools support test suite designers by providingthe information about which parts of source code arecovered during system execution. Unfortunately, codecoverage tools produce only source code coverageinformation. For a test engineer it is often hard tounderstand what the noncovered parts of the source codedo and how they relate to requirements. We propose ageneric approach that provides design coverage of theexecuted software simplifying the development of newtest suites. We demonstrate our approach on commondesign abstractions such as statecharts and structurediagrams. We implement the design coverage usingtracing and trace analysis framework. Using designcoverage, test suites could be created faster by focussingon untested design elements.