It's not a bug, it's a feature: how misclassification impacts bug prediction

DOI 10.1109/icse.2013.6606585 dblp

Abstract

In a manual examination of more than 7,000 issue reports from the bug databases of five open-source projects, we found 33.8% of all bug reports to be misclassified - that is, rather than referring to a code fix, they resulted in a new feature, an update to documentation, or an internal refactoring. This misclassification introduces bias in bug prediction models, confusing bugs and features: On average, 39% of files marked as defective actually never had a bug. We discuss the impact of this misclassification on earlier studies and recommend manual data validation for future studies.

BibTeX

@inproceedings{Herzig-al:ICSE13,
  author    = {Kim Herzig and
               Sascha Just and
               Andreas Zeller},
  title     = {It's not a bug, it's a feature: how misclassification impacts bug prediction},
  booktitle = {ICSE},
  pages     = {392--401},
  publisher = {{IEEE} Computer Society},
  year      = {2013},
}

It's not a bug, it's a feature: how misclassification impacts bug prediction

Abstract

Related papers