2012
DOI: 10.4204/eptcs.86.1
|View full text |Cite
|
Sign up to set email alerts
|

Using Constraints for Equivalent Mutant Detection

Abstract: In mutation testing the question whether a mutant is equivalent to its program is important in order to compute the correct mutation score. Unfortunately, answering this question is not always possible and can hardly be obtained just by having a look at the program's structure. In this paper we introduce a method for solving the equivalent mutant problem using a constraint representation of the program and its mutant. In particularly the approach is based on distinguishing test cases, i.e., test inputs that fo… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
14
0

Year Published

2014
2014
2019
2019

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 20 publications
(15 citation statements)
references
References 16 publications
(15 reference statements)
0
14
0
Order By: Relevance
“…mutants Adamopoulos et al [29] 2004 ----Reduce Co-evolution can help in reducing the effects of eq. mutants Grun et al [30] 2009 Nica and Wotawa [34] implemented a similar constraintbased approach to detect equivalent mutants and demonstrated that many equivalent mutants can be detected. Voas and McGraw [26] suggested that program slicing can help in detecting equivalent mutants.…”
Section: B Equivalent Mutantsmentioning
confidence: 99%
“…mutants Adamopoulos et al [29] 2004 ----Reduce Co-evolution can help in reducing the effects of eq. mutants Grun et al [30] 2009 Nica and Wotawa [34] implemented a similar constraintbased approach to detect equivalent mutants and demonstrated that many equivalent mutants can be detected. Voas and McGraw [26] suggested that program slicing can help in detecting equivalent mutants.…”
Section: B Equivalent Mutantsmentioning
confidence: 99%
“…The Mutation Schemata technique [34] was originally developed in order to factorize the compilation costs of hundreds of similar mutants. Static analysis has been proposed for the "equivalent mutant detection" problem [21], [20] in a way similar to what is sketched in Section VII.…”
Section: Related Workmentioning
confidence: 99%
“…Often enough faults are injected into constructed software and then corresponding mutants are distinguished [4,5]. In this paper, we propose to derive distinguishing sequences not for code but for two EFSMs injecting faults into the template Java implementation of the specification EFSM.…”
Section: Introductionmentioning
confidence: 99%
“…Using the tool Java [8] a number of mutants is generated for the template EFSM implementation which are tested using the initial test suite derived by covering appropriate paths in the specification EFSM. If a mutant is not detected by the initial test suite then a corresponding fault is easily mapped into an EFSM fault and a distinguishing sequence is derived not for two software programs that is known to be a very complex task [5] but for two finite state models that is known to be much simpler [9,10]. First results have been published in [11]; in this paper, we extend a proposed approach to arbitrary EFSMs.…”
Section: Introductionmentioning
confidence: 99%