Do code reviews lead to fewer code smells?

buir.contributor.authorTuna, Erdem
buir.contributor.authorTüzün, Eray
buir.contributor.orcidTuna, Erdem|0000-0001-7137-6361
buir.contributor.orcidTüzün, Eray|0000-0002-5550-7816
dc.citation.epage112101-21
dc.citation.spage112101-1
dc.citation.volumeNumber215
dc.contributor.authorTuna, Erdem
dc.contributor.authorSeaman, Carolyn
dc.contributor.authorTüzün, Eray
dc.date.accessioned2025-02-27T06:28:13Z
dc.date.available2025-02-27T06:28:13Z
dc.date.issued2024-09
dc.departmentDepartment of Computer Engineering
dc.description.abstract**Context:** The code review process is conducted by software teams with various motivations. Among other goals, code reviews act as a gatekeeper for software quality. **Objective:** In this study, we explore whether code reviews have an impact on one specific aspect of software quality, software maintainability. We further extend our investigation by analyzing whether code review process quality (as evidenced by the presence of code review process smells) influences software maintainability (as evidenced by the presence of code smells). **Method:** We investigate whether smells in the code review process are related to smells in the code that was reviewed by using correlation analysis. We augment our quantitative analysis with a focus group study to learn practitioners’ opinions. **Results:** Our investigations revealed that the level of code smells neither increases nor decreases in 8 out of 10 code reviews, regardless of the quality of the code review. Contrary to our own intuition and that of the practitioners in our focus groups, we found that code review process smells have little to no correlation with the level of code smells. We identified multiple potential reasons behind the counter-intuitive results based on our focus group data. Furthermore, practitioners still believe that code reviews are helpful in improving software maintainability. **Conclusion:** Our results imply that the community should update our goals for code review practices and reevaluate those practices to align them with more relevant and modern realities.
dc.embargo.release2026-09-01
dc.identifier.doi10.1016/j.jss.2024.112101
dc.identifier.eissn1873-1228
dc.identifier.issn0164-1212
dc.identifier.urihttps://hdl.handle.net/11693/116889
dc.language.isoEnglish
dc.publisherElsevier Inc.
dc.relation.isversionofhttps://doi.org/10.1016/j.jss.2024.112101
dc.rightsCC BY 4.0 DEED (Attribution 4.0 International)
dc.rights.urihttps://creativecommons.org/licenses/by/4.0/
dc.source.titleThe Journal of Systems and Software
dc.subjectCode reviews
dc.subjectCode review smells
dc.subjectProcess smells
dc.subjectCode smells
dc.subjectFocus group
dc.subjectEmpirical study
dc.subjectMining software repositories
dc.titleDo code reviews lead to fewer code smells?
dc.typeArticle

Files

Original bundle

Now showing 1 - 1 of 1
No Thumbnail Available
Name:
Do_code_reviews_lead_to_fewer_code_smells.pdf
Size:
1.57 MB
Format:
Adobe Portable Document Format

License bundle

Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.71 KB
Format:
Item-specific license agreed upon to submission
Description: