A large-scale empirical study of just-in-time quality assurance

• Published in: IEEE transactions on software engineering 2013-06, Vol.39 (6), p.757-773
• Main Authors: Kamei, Y., Shihab, E., Adams, B., Hassan, A. E., Mockus, A., Sinha, A., Ubayashi, N.
• Format: Article
• Language: English
• Subjects: Accuracy; Computer programs; Construction; Cost reduction; defect prediction; Defects; Developers; Entropy; Just in time; just-in-time prediction; Maintenance; Mathematical models; Measurement; mining software repositories; Object oriented modeling; Packages; Predictive models; Quality assurance; Quality control; Risk assessment; Software; Software engineering; software metrics; Software quality; Studies
• ISSN: 0098-5589; 1939-3520
• DOI: 10.1109/TSE.2012.70

Defect prediction models are a well-known technique for identifying defect-prone files or packages such that practitioners can allocate their quality assurance efforts (e.g., testing and code reviews). However, once the critical files or packages have been identified, developers still need to spend considerable time drilling down to the functions or even code snippets that should be reviewed or tested. This makes the approach too time consuming and impractical for large software systems. Instead, we consider defect prediction models that focus on identifying defect-prone ("risky") software changes instead of files or packages. We refer to this type of quality assurance activity as "Just-In-Time Quality Assurance," because developers can review and test these risky changes while they are still fresh in their minds (i.e., at check-in time). To build a change risk model, we use a wide range of factors based on the characteristics of a software change, such as the number of added lines, and developer experience. A large-scale study of six open source and five commercial projects from multiple domains shows that our models can predict whether or not a change will lead to a defect with an average accuracy of 68 percent and an average recall of 64 percent. Furthermore, when considering the effort needed to review changes, we find that using only 20 percent of the effort it would take to inspect all changes, we can identify 35 percent of all defect-inducing changes. Our findings indicate that "Just-In-Time Quality Assurance" may provide an effort-reducing way to focus on the most risky changes and thus reduce the costs of developing high-quality software.