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

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....

Full description

Saved in:
Bibliographic Details
Main Authors: Herzig, Kim, Just, Sascha, Zeller, Andreas
Format: Conference Proceeding
Language:English
Subjects:
Social and professional topics > Professional topics > Management of computing and information systems > Project and people management
Social and professional topics > Professional topics > Management of computing and information systems > Software management
Software and its engineering > Software creation and management > Software development process management
Software and its engineering > Software creation and management > Software verification and validation > Software defect analysis > Software testing and debugging
Software and its engineering > Software notations and tools > Software configuration management and version control systems
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary: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.
DOI:10.5555/2486788.2486840