| Evaluation of mutation testing for object-oriented programs |
| Full text |
Pdf
(121 KB)
|
| Source
|
International Conference on Software Engineering
archive
Proceedings of the 28th international conference on Software engineering
table of contents
Shanghai, China
SESSION: Emerging results: formal methods and analysis
table of contents
Pages: 869 - 872
Year of Publication: 2006
ISBN:1-59593-375-1
|
|
Authors
|
|
| Sponsors |
|
| Publisher |
|
| Bibliometrics |
Downloads (6 Weeks): 21, Downloads (12 Months): 98, Citation Count: 1
|
|
|
ABSTRACT
The effectiveness of mutation testing depends heavily on the types of faults that the mutation operators are designed to represent. Thus, the quality of the mutation operators is key to mutation testing. Although, mutation operators for object-oriented languages have previously been presented, little research has been done to show the usefulness of the class mutation operators. To assess the usefulness of class mutation operators, we conducted two empirical studies. In the first study, we examine the number and kinds of mutants that are generated for object-oriented programs. In the second study, we investigate the way in which class mutation operators model faults that are not detected by traditional mutation testing. We conducted our studies using a well-known object-oriented system, BCEL.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
BCEL: Byte Code Engineering Library WWW page.
|
| |
2
|
|
| |
3
|
P. Chevalley and P. Thévenod-Fosse. A mutation analysis tool for Java programs. Journal on Software Tools for Technology Transfer (STTT), pages 1--14, December 2002.
|
| |
4
|
S. Kim, J. Clark, and J. McDermid. Class mutation: Mutation testing for object-oriented programs. OOSS: Object-Oriented Software Systems, October 2000.
|
| |
5
|
R. J. Lipton, R. A. DeMillo, and F. G. Sayward. Hints on test data selection: help for the practicing programmer. IEEE Computer, 11(4):34--41, November April.
|
| |
6
|
|
| |
7
|
|
 |
8
|
|
| |
9
|
|
|