Identifying Refactorings from Source-Code Changes
Peter Weißgerber, Stephan Diehl · IEEE/ACM International Conference on Automated Software Engineering (ASE) · 2006
Software has been and is still mostly refactored without tool support. Moreover, as we found in our case studies, programmers tend not to document these changes as refactorings, or even worse label changes as refactorings, although they are not. In this paper we present a technique to detect changes that are likely to be refactorings and rank them according to the likelihood. The evaluation shows that the method has both a high recall and a high precision - it finds most of the refactorings, and most of the found refactoring candidates are really refactorings
Cited by 191 works. doi:10.1109/ase.2006.41
Authors
References
- Refactoring: Improving the Design of Existing Code
- CCFinder: a multilinguistic token-based code clone detection system for large scale source code
- Refactoring object-oriented frameworks
- Populating a Release History Database from version control and bug tracking systems
- Mining version histories to guide software changes
- Mining Version Histories to Guide Software Changes
- Preprocessing CVS data for fine-grained analysis
- Identifying the Semantic and Textual Differences Between Two Versions of a Program
- Identifying the semantic and textual differences between two versions of a program
- Mining version histories to guide software changes