Test-Suite Reduction for Model Based Tests: Effects on Test Quality and Implications for Testing
Proceedings of the 19th IEEE international conference on Automated software engineering
Coverage metrics for requirements-based testing
Proceedings of the 2006 international symposium on Software testing and analysis
On the effect of test-suite reduction on automatically generated model-based tests
Automated Software Engineering
The effect of program and model structure on mc/dc test adequacy coverage
Proceedings of the 30th international conference on Software engineering
Requirements Coverage as an Adequacy Measure for Conformance Testing
ICFEM '08 Proceedings of the 10th International Conference on Formal Methods and Software Engineering
| Hi-index | 0.00 |
Verification and validation of software for safety-critical control systems is a costly and time-consuming activity. Testing is one of the most commonly used methods for verifying such software. Regulatory agencies that certify control systems for use rightly require that the software be tested to certain specified levels of coverage. Developing test-cases to these strict standards takes a good portion of the time and resources and therefore automating this task would result in significant savings. This dissertation develops a framework to automate the generation of such test-cases and addresses some important research challenges. The key hypothesis of this work is that model-checking techniques can be used to automate generation of test-cases from formal behavioral models of software. Various test coverage criteria are formalized using temporal logic and model-checkers are used to obtain valid execution paths from the software model satisfying those temporal formulas. These execution paths, when properly instantiated with data values, become complete test sequences that could then be used to test an implementation. A concrete instantiation of this test generation framework was implemented as part of the NIMBUS toolset for the RSML−e modeling language. The effectiveness and scalability of the approach were evaluated using case studies from the avionics software domain. Data from these studies are presented here and its implications are analyzed. The results point to the potential benefits of this approach as well as some practical limitations. Possible future directions to address those limitations are discussed.