Impact of Change Granularity in Refactoring Detection

TL;DR

This paper investigates how the detection of refactorings varies with different commit granularities, revealing that coarse-grained refactorings are common and important for understanding software evolution.

Contribution

It introduces the concept of coarse-grained refactoring detection and compares it across multiple repositories, highlighting its significance in refactoring research.

Findings

CGRs are prevalent across repositories.

Frequency of CGRs increases with coarser granularity.

Move-related refactorings are most common among CGRs.

Abstract

Detecting refactorings in commit history is essential to improve the comprehension of code changes in code reviews and to provide valuable information for empirical studies on software evolution. Several techniques have been proposed to detect refactorings accurately at the granularity level of a single commit. However, refactorings may be performed over multiple commits because of code complexity or other real development problems, which is why attempting to detect refactorings at single-commit granularity is insufficient. We observe that some refactorings can be detected only at coarser granularity, that is, changes spread across multiple commits. Herein, this type of refactoring is referred to as coarse-grained refactoring (CGR). We compared the refactorings detected on different granularities of commits from 19 open-source repositories. The results show that CGRs are common, and their frequency increases as the granularity becomes coarser. In addition, we found that Move-related refactorings tended to be the most frequent CGRs. We also analyzed the causes of CGR and suggested that CGRs will be valuable in refactoring research.