TY - JOUR
T1 - Deciphering refactoring branch dynamics in modern code review
T2 - An empirical study on Qt
AU - AlOmar, Eman Abdullah
N1 - Publisher Copyright:
© 2024 Elsevier B.V.
PY - 2025/1
Y1 - 2025/1
N2 - Context: Modern code review is a widely employed technique in both industrial and open-source projects, serving to enhance software quality, share knowledge, and ensure compliance with coding standards and guidelines. While code review is extensively studied for its general challenges, best practices, outcomes, and socio-technical aspects, little attention has been paid to how refactoring is reviewed and what developers prioritize when reviewing refactored code in the ‘Refactor’ branch. Objective: The goal is to understand the review process for refactoring changes in the ‘Refactor’ branch and to identify what developers care about when reviewing code in this branch. Method: In this study, we present a quantitative and qualitative examination to understand the main criteria developers use to decide whether to accept or reject refactored code submissions and identify the challenges inherent in this process. Results: Analyzing 2154 refactoring and non-refactoring reviews across Qt open-source projects, we find that reviews involving refactoring from the ‘Refactor’ branch take significantly less time to resolve in terms of code review efforts. Additionally, documentation of developer intent is notably sparse within the ‘Refactor’ branch compared to other branches. Furthermore, through thematic analysis of a substantial sample of refactoring code review discussions, we construct a comprehensive taxonomy consisting of 12 refactoring review criteria. Conclusion: Our findings underscore the importance of developing precise and efficient tools and techniques to aid developers in the review process amidst refactorings.
AB - Context: Modern code review is a widely employed technique in both industrial and open-source projects, serving to enhance software quality, share knowledge, and ensure compliance with coding standards and guidelines. While code review is extensively studied for its general challenges, best practices, outcomes, and socio-technical aspects, little attention has been paid to how refactoring is reviewed and what developers prioritize when reviewing refactored code in the ‘Refactor’ branch. Objective: The goal is to understand the review process for refactoring changes in the ‘Refactor’ branch and to identify what developers care about when reviewing code in this branch. Method: In this study, we present a quantitative and qualitative examination to understand the main criteria developers use to decide whether to accept or reject refactored code submissions and identify the challenges inherent in this process. Results: Analyzing 2154 refactoring and non-refactoring reviews across Qt open-source projects, we find that reviews involving refactoring from the ‘Refactor’ branch take significantly less time to resolve in terms of code review efforts. Additionally, documentation of developer intent is notably sparse within the ‘Refactor’ branch compared to other branches. Furthermore, through thematic analysis of a substantial sample of refactoring code review discussions, we construct a comprehensive taxonomy consisting of 12 refactoring review criteria. Conclusion: Our findings underscore the importance of developing precise and efficient tools and techniques to aid developers in the review process amidst refactorings.
KW - Code review
KW - Developer perception
KW - Refactoring
KW - Software quality
UR - http://www.scopus.com/inward/record.url?scp=85206299062&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85206299062&partnerID=8YFLogxK
U2 - 10.1016/j.infsof.2024.107596
DO - 10.1016/j.infsof.2024.107596
M3 - Article
AN - SCOPUS:85206299062
SN - 0950-5849
VL - 177
JO - Information and Software Technology
JF - Information and Software Technology
M1 - 107596
ER -