2012
DOI: 10.1007/978-3-642-28872-2_28
|View full text |Cite
|
Sign up to set email alerts
|

On the Danger of Coverage Directed Test Case Generation

Abstract: Abstract. In the avionics domain, the use of structural coverage criteria is legally required in determining test suite adequacy. With the success of automated test generation tools, it is tempting to use these criteria as the basis for test generation. To more firmly establish the effectiveness of such approaches, we have generated and evaluated test suites to satisfy two coverage criteria using counterexample-based test generation and a random generation approach, contrasted against purely random test suites… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

3
45
0

Year Published

2015
2015
2019
2019

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 55 publications
(48 citation statements)
references
References 30 publications
(51 reference statements)
3
45
0
Order By: Relevance
“…(The Simulink Coder is not a trusted code generator; thus, the generated code must be subjected to rigorous conformance testing demonstrating that no faults were introduced in the code generation. This testing is outside the scope of this paper but in can be fully automated as extensively discussed in our previous work [7,22,25]) Although the process of code generation from the model is straightforward, installing the software on the actual hardware can be a challenge. Below we discuss the challenges we faced while integrating the device with the generated code and discuss the approaches we took to address them.…”
Section: Gpca Implementationmentioning
confidence: 99%
“…(The Simulink Coder is not a trusted code generator; thus, the generated code must be subjected to rigorous conformance testing demonstrating that no faults were introduced in the code generation. This testing is outside the scope of this paper but in can be fully automated as extensively discussed in our previous work [7,22,25]) Although the process of code generation from the model is straightforward, installing the software on the actual hardware can be a challenge. Below we discuss the challenges we faced while integrating the device with the generated code and discuss the approaches we took to address them.…”
Section: Gpca Implementationmentioning
confidence: 99%
“…As discussed in the introduction, the effectiveness of coverage criteria is still a very active research topic (Gopinath et al 2014;Inozemtseva and Holmes 2014;Kochhar et al 2015;Staats et al 2012). However, the studies evaluating the effectiveness of coverage measures consider the faults (or mutations) as having same importance and do not take into account their respective probability of failure.…”
Section: Related Workmentioning
confidence: 99%
“…On the other side, we observe that almost all studies assessing the effectiveness of coverage testing have used as a measure of effectiveness the faults (or mutations) detected without distinguishing their probability of failure in use (e.g., Inozemtseva and Holmes 2014;Kochhar et al 2015;Staats et al 2012;Wei et al 2012;Wong et al 1994, just to cite a few). Thus, we still know little about how (and if) coverage testing is related to delivered reliability (Frankl et al 1998).…”
Section: Introductionmentioning
confidence: 99%
See 2 more Smart Citations