by Nicolas Bettenburg · Sascha Just · Adrian Schröter · Cathrin Weiss · Rahul Premraj · Thomas Zimmermann at FSE 2008
In software development, bug reports provide crucial information to developers. However, these reports widely differ in their quality. We conducted a survey among developers and users of APACHE, ECLIPSE, and MOZILLA to find out what makes a good bug report. The analysis of the 466 responses revealed an information mismatch between what developers need and what users supply. Most developers consider steps to reproduce, stack traces, and test cases as helpful, which are at the same time most difficult to provide for users. Such insight is helpful to design new bug tracking tools that guide users at collecting and providing more helpful information. Our CUEZILLA prototype is such a tool and measures the quality of new bug reports; it also recommends which elements should be added to improve the quality. We trained CUEZILLA on a sample of 289 bug reports, rated by developers as part of the survey. In our experiments, CUEZILLA was able to predict the quality of 31–48% of bug reports accurately.
My talk at FSE 2008
Reference
-
[2008,inproceedings] bibtexN. Bettenburg, S. Just, A. Schröter, C. Weiss, R. Premraj, and T. Zimmermann, "What Makes a Good Bug Report?," in SIGSOFT ’08/FSE-16: Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering, 2008, pp. 308-318.
@inproceedings{bettenburg:fse:2008,
author = {Bettenburg, Nicolas and Just, Sascha and Schr\"{o}ter, Adrian and Weiss, Cathrin and Premraj, Rahul and Zimmermann, Thomas},
Booktitle = {SIGSOFT '08/FSE-16: Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering},
Pages = {308--318},
Publisher = {ACM},
Title = {What Makes a Good Bug Report?},
Year = {2008}
}
Hi Rahul, it was very interesting to attend your presentation in ISEC 2009. I am wondering if you can share your presentation? It is not there on the CD. Thanks.
[Reply]