2016 IEEE Ninth International Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2016
DOI: 10.1109/icstw.2016.29
|View full text |Cite
|
Sign up to set email alerts
|

Nequivack: Assessing Mutation Score Confidence

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
9
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 12 publications
(9 citation statements)
references
References 21 publications
0
9
0
Order By: Relevance
“…A different attempt to solve the same problem is based on identifying killable mutants. This has been attempted using (static) symbolic execution [149,156]. Such attempts aim at executing mutants symbolically in order to identify whether these can be killable with symbolic input data.…”
Section: Identifying Equivalent Mutantsmentioning
confidence: 99%
See 1 more Smart Citation
“…A different attempt to solve the same problem is based on identifying killable mutants. This has been attempted using (static) symbolic execution [149,156]. Such attempts aim at executing mutants symbolically in order to identify whether these can be killable with symbolic input data.…”
Section: Identifying Equivalent Mutantsmentioning
confidence: 99%
“…Other attempts are due to Papadakis and Malevris [177] and Holling et al [156] who used out of the box symbolic execution engines (JPF-SE [178] and KLEE [179] respectively) to generate mutation-based test cases. These approaches instrument the original program with mutant killing conditions that the symbolic execution engine is asked to cover (transforms the mutant killing problem to code reachability problem).…”
Section: Static Constraint-based Test Generationmentioning
confidence: 99%
“…reliance on dedicated hardware, emulators, and simulators also prevents the use of static program analysis to detect equivalent mutants [21], [22], [23]. Such characteristics are common to embedded software in other types of CPS domains including avionics, automotive, and industry 4.0 (e.g., robotics systems).…”
Section: Textmentioning
confidence: 99%
“…Bardin et al proposed program verification to exclude test cases that cannot reach the mutant and/or that cannot infect the program state [4]. Other authors have explored using (static) symbolic execution techniques to identify whether a test case can detect mutants [15,28]. An example of a tool implementing this approach is PIT [8], that executes only those test cases that have a chance to kill the mutant, i.e.…”
Section: Existing Techniquesmentioning
confidence: 99%
“…Second, program verification excludes test cases which cannot reach the mutant and/or which cannot infect the program state [4]. Third, (static) symbolic execution techniques identify whether a test case is capable of killing the mutant [15,28]. This paper explores an alternative technique: fine-grained traceability links via focal methods [12].…”
Section: Introductionmentioning
confidence: 99%