• Publications
  • Influence
A large-scale empirical study of just-in-time quality assurance
TLDR
We consider defect prediction models that focus on identifying defect-prone (“risky”) software changes instead of files or packages. Expand
  • 282
  • 48
  • PDF
The impact of code review coverage and code review participation on software quality: a case study of the qt, VTK, and ITK projects
TLDR
Software code review, i.e., the practice of having third-party team members critique changes to a software system, is a well-established best practice in both open source and proprietary software domains. Expand
  • 203
  • 18
  • PDF
An empirical study of the impact of modern code review practices on software quality
TLDR
Software code review, i.e., the practice of having other team members critique changes to a software system, is a well-established best practice in both open source and proprietary software domains. Expand
  • 150
  • 11
  • PDF
Studying just-in-time defect prediction using cross-project models
TLDR
We empirically evaluate the performance of Just-In-Time (JIT) defect prediction models in a cross-project context. Expand
  • 107
  • 10
  • PDF
Revisiting common bug prediction findings using effort-aware models
TLDR
We revisit two common findings in the bug prediction literature: 1) Process metrics (e.g., change history) outperform product metrics when considering quality assurance efforts when evaluating the effectiveness of prediction models. Expand
  • 162
  • 9
  • PDF
An empirical study of just-in-time defect prediction using cross-project models
TLDR
We empirically evaluate the performance of JIT cross-project models, i.e., models learned from older projects with sufficient history. Expand
  • 103
  • 9
  • PDF
Are Fix-Inducing Changes a Moving Target? A Longitudinal Case Study of Just-In-Time Defect Prediction
TLDR
JIT models are trained using techniques that assume that past fix-inducing changes are similar to future ones. Expand
  • 50
  • 9
  • PDF
Studying re-opened bugs in open source software
TLDR
Re-opened bugs increase maintenance costs, degrade the overall user-perceived quality of the software and lead to unnecessary rework. Expand
  • 104
  • 8
  • PDF
High-impact defects: a study of breakage and surprise defects
TLDR
We find that surprise defects are related to incomplete requirements and that the common assumption that a fix is caused by a previous change does not hold in this project. Expand
  • 83
  • 7
  • PDF
Predicting Re-opened Bugs: A Case Study on the Eclipse Project
TLDR
We study and predict re-opened bugs through a case study on the Eclipse project. Expand
  • 96
  • 7
  • PDF
...
1
2
3
4
5
...