Do Null-Type Mutation Operators Help Prevent Null-Type Faults?
arXiv:2004.04211 · doi:10.1007/978-3-030-10801-4_33
Abstract
The null-type is a major source of faults in Java programs, and its overuse has a severe impact on software maintenance. Unfortunately traditional mutation testing operators do not cover null-type faults by default, hence cannot be used as a preventive measure. We address this problem by designing four new mutation operators which model null-type faults explicitly. We show how these mutation operators are capable of revealing the missing tests, and we demonstrate that these mutation operators are useful in practice. For the latter, we analyze the test suites of 15 open-source projects to describe the trade-offs related to the adoption of these operators to strengthen the test suite.
References in corpus (5)
- Evaluating Random Mutant Selection at Class-Level in Projects with Non-Adequate Test Suites
- Considering Polymorphism in Change-Based Test Suite Reduction
- Mutation Testing as a Safety Net for Test Code Refactoring
- A Model to Estimate First-Order Mutation Coverage from Higher-Order Mutation Coverage
- C++11/14 Mutation Operators Based on Common Fault Patterns