An empirical study on developer‐related factors characterizing fix‐inducing commits. Issue 1 (21st June 2016)

• Record Type: Journal Article
• Authors: Tufano, Michele; Bavota, Gabriele; Poshyvanyk, Denys; Di Penta, Massimiliano; Oliveto, Rocco; De Lucia, Andrea
• Is Part Of: Journal of software. Volume 29:Issue 1(2017)
• Page Start: n/a
• Page End: n/a
• Publication Date: 2016-06-21
• Subjects: commits -- bug introduction -- empirical study; Software engineering -- Periodicals; Computer software -- Development -- Periodicals; Software maintenance -- Periodicals; 005.1
• DOI: 10.1002/smr.1797
• Languages: English
• ISSNs: 2047-7473

Abstract

Abstract: This paper analyzes developer‐related factors that could influence the likelihood for a commit to induce a fix. Specifically, we focus on factors that could potentially hinder developers' ability to correctly understand the code components involved in the change to be committed as follows: (i) the coherence of the commit (i.e., how much it is focused on a specific topic); (ii) the experience level of the developer on the files involved in the commit; and (iii) the interfering changes performed by other developers on the files involved in past commits. The results of our study indicate that 'fix‐inducing' commits (i.e., commits that induced a fix) are significantly less coherent than 'clean' commits (i.e., commits that did not induce a fix). Surprisingly, 'fix‐inducing' commits are performed by more experienced developers; yet, those are the developers performing more complex changes in the system. Finally, 'fix‐inducing' commits have a higher number of past interfering changes as compared with 'clean' commits. Our empirical study sheds light on previously unexplored factors and presents significant results that can be used to improve approaches for defect prediction. Copyright © 2016 John Wiley & Sons, Ltd.