Generation of Optimized Testsuites for UML Statecharts with Time

Using mutation to design tests for aspect-oriented models. Technology, http://dx.doi.org/10. 1016/j.infsof.2016.04.007 Access to the published version may require subscription. N.B. When citing this work, cite the original published paper. Information and Software AbstractContext: Testing for properties such as robustness or security is complicated because their concerns are often repeated in many locations and muddled with the normal code. Such "cross-cutting concerns" include things like interrupt events, exception handling, and security protocols. Aspect-oriented (AO) modeling allows developers to model the cross-cutting behavior independently of the normal behavior, thus supporting model-based testing of cross-cutting concerns. However, mutation operators defined for AO programs (source code) are usually not applicable to AO models (AOMs) and operators defined for models do not target the AO features.Objective: We present a method to design abstract tests at the aspect-oriented model level. We define mutation operators for aspect-oriented models and evaluate the generated mutants for an example system. Method: AOMs are mutated with novel operators that specifically target the AO modeling features. Test traces killing these mutant models are then generated. The generated and selected traces are abstract tests that can be transformed to concrete black-box tests and run on the implementation level, to evaluate the behavior of the woven cross-cutting concerns (combined aspect and base models). Results: This paper is a significant extension of our paper at Mutation 2015. We present a complete fault model, additional mutation operators, and a thorough analysis of the mutants generated for an example system. Conclusions: The analysis shows that some mutants are stillborn (syntactically illegal) but none is equivalent (exhibiting the same behavior as the original model). Additionally, our AOM-specific mutation operators can be combined with pre-existing operators to mutate code or models without any overlap.

show abstract

“…Mücke and Huhn [41] describe how to transform a UML state chart to Uppaal. We then used the Uppaal model checker to verify its behavior [33].…”

Section: Example Systemmentioning

confidence: 99%

Using mutation to design tests for aspect-oriented models

Lindström

Offutt

Sundmark

et al. 2017

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…In [1] it is shown, how models are instrumented and properties are generated to achieve state coverage, transition coverage, modified condition/decision coverage, boundary coverage and dataflow coverage. The instrumentation adds new coverage variables to the system, which are set, whenever a partial coverage is achieved.…”

Section: Coverage Criteriamentioning

confidence: 99%

“…In [1] we investigate a technique to generate the time optimal testsuite. We achieved a significant reduction in test execution time, but the technique suffers from high memory consumption, i.e.…”

Section: Strategies To Generate Time Optimized Testsuitesmentioning

confidence: 99%

“…The different instrumentations are described in Section 2. The details on the translation from UML statecharts [9] to the input language of the UPPAAL model checker [10] and back can be found in [1]. Section 3 is concerned with the combination of search heuristics for test case generation and min-set-cover algorithms to optimize testsuites with respect to test execution time.…”

Section: Introductionmentioning

confidence: 99%

“…Unfortunately, the execution of the generated test suites tend to be rather time-consuming. In [1] we presented a method to generate the test suites with the shortest execution time providing the required coverage, but this method can only be applied to small models due to memory-consumption. Here we show how to generate test suites for a number of different test quality criteria like coverage criteria, UIOs, mutant testing.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Minimizing Test Execution Time During Test Generation

Mücke

Huhn

Software Engineering Techniques: Design for Quality

Self Cite

View full text Add to dashboard Cite

Abstract. In the area of model based testing, major improvements have been made in the generation of conformance tests using a model checker. Unfortunately, the execution of the generated test suites tend to be rather time-consuming. In [1] we presented a method to generate the test suites with the shortest execution time providing the required coverage, but this method can only be applied to small models due to memory-consumption. Here we show how to generate test suites for a number of different test quality criteria like coverage criteria, UIOs, mutant testing. Moreover, we present heuristics to significantly reduce test execution time that are as efficient as a naive testsuite generation. Our optimization combines min-set-cover-algorithms and search strategies, which we use to enlengthen generated test cases by promising additional coverages. We compare several heuristics and present a case study where we could achieve a reduction of the test execution time to less than 10%.

show abstract

A formal analysis of MCDC and RCDC test criteria

Kapoor¹,

Bowen²

2005

Softw. Test. Verif. Reliab.

View full text Add to dashboard Cite

Generation of Optimized Testsuites for UML Statecharts with Time

Cited by 11 publications

References 19 publications

Using mutation to design tests for aspect-oriented models

Using mutation to design tests for aspect-oriented models

Minimizing Test Execution Time During Test Generation

A formal analysis of MCDC and RCDC test criteria

Contact Info

Product

Resources

About