What Makes a Good Bug Report?

By Thomas Zimmermann, Rahul Premraj, Nicolas Bettenburg, Sascha Just, Adrian Schröter, Cathrin Weiss. IEEE Transactions on Software Engineering, 2008

936 citations recorded by the source corpus.

Subfields: Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/21fa1dba8539598210496cfcdb853fef719a0805

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

1. Sunghun Kim
2. Hongyu Zhang
3. David Lo
4. Xin Ye
5. Chang Liu
6. Razvan C. Bunescu
7. Walid Maalej
8. Thomas Zimmermann

In Software

1. Sunghun Kim
2. Hongyu Zhang
3. David Lo
4. Xin Ye
5. Chang Liu
6. Razvan C. Bunescu
7. Thomas Zimmermann
8. Walid Maalej

Citations in the corpus

• Bug report, feature request, or simply praise? On automatically classifying app reviews (2015, methodology): “Bug repositories are perhaps the most studied tools for collecting user feedback in software projects [3], mainly from the development and maintenance perspective.”
• Improving bug triage with bug tossing graphs (2009, background): “Several studies investigated which factors predict the lifetime of bug reports, that is from submission to being closed [4, 19, 21].”
• User feedback in the appstore: An empirical study (2013, background): “This hinders developers from improving their apps only from this textual feedback [20].”
• Automatic creation of SQL Injection and cross-site scripting attacks (2009, background): “The attack generator and checker ensure that A creates concrete exploits, which are are much easier for programmers to fix than reports of abstract traces [4, 8].”
• A discriminative model approach for accurate duplicate bug report retrieval (2010, background): “After that, Bettenburg et al. made a survey on the developers of several well-known open source projects (Eclipse, Mozilla, and Apache) to study the factors that developers cared most on dealing with bug reports [3].”
• Learning to rank relevant files for bug reports using domain knowledge (2014, background): “Lexical mismatches between natural language statements in bug reports and technical terms in software systems [4] limit the accuracy of ranking methods that are based on simple lexical matching scores.”
• Duplicate bug reports considered harmful … really? (2008, methodology): “In previous work, we conducted a survey on the quality of bug reports and frequent problems in bug reporting [3] [4].”
• Towards more accurate retrieval of duplicate bug reports (2011, background): “survey developers of Eclipse, Mozilla, and Apache to study what developers care most in a bug report [24].”
• Predicting the severity of a reported bug (2010, background): “Researchers have been investigating what characterizes a “good” bug report, i.e., ones that are appreciated by developers and are likely to get fixed sooner [7].”
• Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports (2012, background): “Many researchers mine bug report information to solve software engineering problems such as duplicate bug detection [33, 35], automatic bug triage [4, 7], bug report quality analysis [6, 7], and defect prediction [20, 37].”