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

By Yasutaka Kamei, Emad Shihab, Bram Adams, Ahmed E. Hassan, Audris Mockus, Anand Sinha, Naoyasu Ubayashi. IEEE Transactions on Software Engineering, 2013

694 citations recorded by the source corpus.

Subfields: Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/04eb410c0a59fc08a4648af43f7de323cc7d06c2

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Software

Citations in the corpus

Online Defect Prediction for Imbalanced Data (2015, methodology): “Cross-validation is a commonly used method to evaluate the prediction models [1], [7], [8], [14], [17], [26].”
The impact of code review coverage and code review participation on software quality: a case study of the qt, VTK, and ITK projects (2014, methodology): “prior work [18], we define post-release defects as those with fixes recorded in the six-month period after the release date.”
The Impact of Class Rebalancing Techniques on the Performance and Interpretation of Defect Prediction Models (2018, background): “, cross-project defect prediction [98], just-in-time defect prediction [34], heterogenous defect prediction [59]).”
An empirical study of the impact of modern code review practices on software quality (2015, methodology): “…regression models that are built to explain the incidence of post-release defects (i.e., defects in ofﬁcial releases of a software product), which is a popular proxy for software quality (Bird et al. , 2011; Hassan, 2009; Kamei et al. , 2013; Mockus and Weiss, 2000; Nagappan and Ball, 2007).”
Deep Learning for Just-in-Time Defect Prediction (2015, methodology): “perform a large-scale empirical study on just-in-time defect prediction, and propose the usage of the logistic regression algorithm to build a prediction model [1].”
Improving Code Localization with Repository Memory (2025, unknown): “We structure this historical data into two complementary memory stores, designed Missing import statement in generated migration (NameError: name 'models' is not defined) -----------------------------------------------------------------------------------------------------------”