Automatically repairing test cases for evolving method declarations

Authors:
Mehdi Mirzaaghaei;Fabrizio Pastore;Mauro Pezze
Affiliations:
University of Lugano, Switzerland;University of Lugano, Switzerland;University of Lugano, Switzerland
Venue:
ICSM '10 Proceedings of the 2010 IEEE International Conference on Software Maintenance
Year:
2010

Citing 0
Cited 3

ReAssert: a tool for repairing broken unit tests

Proceedings of the 33rd International Conference on Software Engineering
Automatic test suite evolution

Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Is it dangerous to use version control histories to study source code evolution?

ECOOP'12 Proceedings of the 26th European conference on Object-Oriented Programming

Quantified Score

Hi-index	0.00

Visualization

Abstract

When software systems evolve, for example due to fault fixes, modification of functionalities or refactoring activities, test cases may become obsolete thus generating wrong results or even not being executable or compilable. Maintaining test cases is expensive and time consuming, and often test cases are discarded by software developers due to high maintenance costs. This paper presents TestCareAssistant, a technique that combines data-flow analysis with program diffing for automatically repairing test cases that become obsolete because of changes in method declarations (addition, removal, or type modification of parameters or return values). The paper illustrates the efficacy of TestCareAssistant by analyzing the impact of method declarations changes on the executability of test cases, and by presenting the preliminary results of applying TestCareAssistant to repair 22 test cases.