Mutation Testing as a Safety Net for Test Code Refactoring
Ali Parsai, Alessandro Murgia, Quinten David Soetens, Serge Demeyer

TL;DR
This paper proposes using mutation testing to ensure test code behavior remains consistent after refactoring and to identify improperly refactored test code segments.
Contribution
It introduces a novel approach applying mutation testing as a safety net for test code refactoring, enhancing code quality assurance.
Findings
Mutation testing can verify test code behavior preservation.
The approach helps identify improperly refactored test segments.
It improves confidence in test code refactoring processes.
Abstract
Refactoring is an activity that improves the internal structure of the code without altering its external behavior. When performed on the production code, the tests can be used to verify that the external behavior of the production code is preserved. However, when the refactoring is performed on test code, there is no safety net that assures that the external behavior of the test code is preserved. In this paper, we propose to adopt mutation testing as a means to verify if the behavior of the test code is preserved after refactoring. Moreover, we also show how this approach can be used to identify the part of the test code which is improperly refactored.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
