29th Annual International Computer Software and Applications Conference (COMPSAC'05)
DOI: 10.1109/compsac.2005.66
|View full text |Cite
|
Sign up to set email alerts
|

Coverage-Directed Test Generation with Model Checkers: Challenges and Opportunities

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(9 citation statements)
references
References 10 publications
0
9
0
Order By: Relevance
“…7 We do not reject H01 for the DWM 1 case example when using MC/DC coverage and the output-only oracle, nor do we reject H01 for the Docking Approach case example. 8 In our previous work we found the opposite effect [34].…”
Section: Evaluation Of Rq1 and Rq2mentioning
confidence: 92%
See 1 more Smart Citation
“…7 We do not reject H01 for the DWM 1 case example when using MC/DC coverage and the output-only oracle, nor do we reject H01 for the Docking Approach case example. 8 In our previous work we found the opposite effect [34].…”
Section: Evaluation Of Rq1 and Rq2mentioning
confidence: 92%
“…Other measurements exist, e.g., the time required to generate and/or execute tests [34]. We chose size to be favorable towards directed test generation.…”
Section: Threats To Validitymentioning
confidence: 99%
“…If a property is not satisfied, the model checker attempts to generate a counterexample in the form of a trace as a sequence of states [5]. The idea of using traces of counterexamples as test sequences is not new and investigated in various works [5], [6], [7], [8], [9]. Other approaches, such as mutant-based model checking to ensure safety properties [10], exists in the literature.…”
Section: Introduction and Related Workmentioning
confidence: 99%
“…In a consequent experiment, Devaraj et al [108] showed that while coverage criteria are suitable for analysis purposes, there are problems when using them for test case generation. The identified problem is that coverage of a trap property does not guarantee that a considered part of the specification is actually executed by the resulting test case.…”
Section: Quality Concerns For Coverage Based Testingmentioning
confidence: 99%