An extended fault class hierarchy for specification-based testing
ACM Transactions on Software Engineering and Methodology (TOSEM)
Property relevant software testing with model-checkers
ACM SIGSOFT Software Engineering Notes
Using LTL rewriting to improve the performance of model-checker based test-case generation
Proceedings of the 3rd international workshop on Advances in model-based testing
Relating counterexamples to test cases in CTL model checking specifications
Proceedings of the 3rd international workshop on Advances in model-based testing
Using model-checkers to generate and analyze property relevant test-cases
Software Quality Control
Generating Tests from B Specifications and Test Purposes
ABZ '08 Proceedings of the 1st international conference on Abstract State Machines, B and Z
Complementary Criteria for Testing Temporal Logic Properties
TAP '09 Proceedings of the 3rd International Conference on Tests and Proofs
Issues in using model checkers for test case generation
Journal of Systems and Software
Hybrid testing and verification techniques for a cognitive radio system
SEA '07 Proceedings of the 11th IASTED International Conference on Software Engineering and Applications
Specification-based testing for COCASL'S modal specifications
CALCO'07 Proceedings of the 2nd international conference on Algebra and coalgebra in computer science
Security mutants for property-based testing
TAP'11 Proceedings of the 5th international conference on Tests and proofs
Fault-based test suite prioritization for specification-based testing
Information and Software Technology
Automatic verification and conformance testing for validating safety properties of reactive systems
FM'05 Proceedings of the 2005 international conference on Formal Methods
Hi-index | 0.00 |
Abstract: In addition to providing a sound basis for analysis, formal methods can support other development activities; in our case the target is specification-based testing at the system level. We use the formal method of model checking to either generate new test sets or analyze existing test sets with respect to safety properties expressed in a temporal logic. We consider two types of tests: failing tests, in which a system must reject (fail) a specific dangerous action, and passing tests, in which a system must accept (pass) a safe action in a context that also includes a plausible dangerous action. We formalize our notion of dangerous actions with a mutation model for model checking specifications, and we develop coverage criteria to assess test sets. The coverage criteria are based on the logic operators from the Computation Tree Logic (CTL) and encompass the idea of scenarios where a dangerous action is either inevitable (A) or possible (E) as of the next state (X) or at some point in the future (F). We demonstrate the feasibility of our approach with an example.