by Nicolas Bettenburg · Sascha Just · Adrian Schröter · Cathrin Weiss · Rahul Premraj · Thomas Zimmermann at eTX ’07
The information in bug reports influences the speed at which bugs are fixed. However, bug reports differ in their quality of information. We conducted a survey among ECLIPSE developers to determine the information in reports that they widely used and the problems frequently encountered. Our results show that steps to reproduce and stack traces are most sought after by developers, while inaccurate steps to reproduce and incomplete information pose the largest hurdles. Surprisingly, developers are indifferent to bug duplicates. Such insight is useful to design new bug tracking tools that guide reporters at providing more helpful information. We also present a prototype of a quality-meter tool that measures the quality
of bug reports by scanning its content.
Talk at eTX ’07 by Nicolas Bettenburg
Reference
-
[2007,inproceedings] bibtexN. Bettenburg, S. Just, A. Schröter, C. Weiß, R. Premraj, and T. Zimmermann, "Quality of bug reports in Eclipse," in eclipse ’07: Procs. of the OOPSLA workshop on eclipse technology eXchange, New York, NY, USA, 2007, pp. 21-25.
@inproceedings{bettenburg:etx:2007, Address = {New York, NY, USA},
Author = {Bettenburg, Nicolas and Just, Sascha and Schr\"{o}ter, Adrian and Wei\ss, Cathrin and Premraj, Rahul and Zimmermann, Thomas},
Booktitle = {eclipse '07: Procs. of the OOPSLA workshop on eclipse technology eXchange},
Pages = {21--25},
Publisher = {ACM},
Title = {Quality of bug reports in Eclipse},
Year = {2007}
}