2013 13th International Conference on Quality Software 2013
DOI: 10.1109/qsic.2013.47
|View full text |Cite
|
Sign up to set email alerts
|

A Comparison of Mutation Analysis Tools for Java

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
15
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 25 publications
(15 citation statements)
references
References 23 publications
0
15
0
Order By: Relevance
“…We use two popular Java mutation tools: PIT 3 [49] and Major 4 , both of which have been widely used in mutation testing research [50], [51]. As our work targets the cost problem of mutation testing, we choose PIT as the primary mutation testing tool since it is evaluated to be very efficient [52]. Moreover, PIT has been demonstrated to be very robust [52], enabling large-scale experimental study.…”
Section: Propagationmentioning
confidence: 99%
See 2 more Smart Citations
“…We use two popular Java mutation tools: PIT 3 [49] and Major 4 , both of which have been widely used in mutation testing research [50], [51]. As our work targets the cost problem of mutation testing, we choose PIT as the primary mutation testing tool since it is evaluated to be very efficient [52]. Moreover, PIT has been demonstrated to be very robust [52], enabling large-scale experimental study.…”
Section: Propagationmentioning
confidence: 99%
“…As our work targets the cost problem of mutation testing, we choose PIT as the primary mutation testing tool since it is evaluated to be very efficient [52]. Moreover, PIT has been demonstrated to be very robust [52], enabling large-scale experimental study. Additionally, to further investigate PMT's performance on different tools, we use Major as an auxiliary tool, because it is also widely adopted and can generate mutants that represent real faults [10].…”
Section: Propagationmentioning
confidence: 99%
See 1 more Smart Citation
“…Similar views on code coverage point out that high coverage do not necessarily indicate that a test suite is effective at catching faults [23]. Mutation testing, on the other hand, is related to test suite effectiveness in terms of test suite's ability to detect faults [4,13,24]. Following the argument by Madeyski [26], we also use mutation score indicator as a measure of unit test effectiveness in this experiment.…”
Section: Unit Testingmentioning
confidence: 99%
“…We could avoid this measurement bias by using multiple measures for unit test effectiveness. The existing studies [4,13,23,24] point out that unit test effectiveness is more associated with mutation score indicator compared to coverage. Therefore, we used mutation score as our construct.…”
Section: Threats To Validitymentioning
confidence: 99%