| |
[
Software Evolution |
Vulnerable Components |
Predicting Failures |
Good Bug Reports |
Related Changes |
Cross-cutting Concerns |
Usage Patterns |
Jazz |
Trends
]
The Software Evolution project at the Software Engineering Chair, Saarland University, analyzes version and bug databases to predict failure-prone modules, related changes, and future development activities.
What's new
- View the talk "Quality of Bug Reports in Eclipse", presented at ETX 2007 in Montreal, Canada. View now...
- Read the technical report "What Makes a Good Bug Report?". Download now...
What Makes a Good Bug Report?
To find out, we conducted a survey among APACHE, ECLIPSE, and MOZILLA
developers. The analysis of the 156 responses shows that steps to
reproduce and stack traces are most sought after, while inaccurate
steps to reproduce and incomplete information pose the largest
hurdles. This insight is helpful to design new bug tracking tools that
guide reporters at providing more helpful information. Our CUEZILLA
prototype is a such tool and provides reporters with feedback on the
quality of new bug reports and recommends to add missing elements.
Papers
- What Makes a Good Bug Report?. Nicolas Bettenburg, Sascha Just, Adrian Schröter, Cathrin Weiß, Rahul Premraj, Thomas Zimmermann.
Technical Report, Saarland University, Saarbrücken, September 2007.
[PDF]
Abstract.
The information in bug reports influences the speed at which bugs are
fixed. However, bug reports differ in their quality of information. In
order to determine the elements that developer widely use to fix bugs
and the problems frequently encountered, we conducted a survey among
APACHE, ECLIPSE, and MOZILLA developers. The analysis of the 156
responses shows that steps to reproduce and stack traces are most
sought after, while inaccurate steps to reproduce and incomplete
information pose the largest hurdles. This insight is helpful to
design new bug tracking tools that guide reporters at providing more
helpful information. Our CUEZILLA prototype is a such tool and
provides reporters with feedback on the quality of new bug reports and
recommends to add missing elements. We trained CUEZILLA on a sample of
289 bug reports, rated by developers as part of the survey. In our
evaluation, CUEZILLA was able to predict the quality of 31-48% of bugs
reports accurately.
- Quality of Bug Reports in Eclipse. Nicolas Bettenburg, Sascha Just, Adrian Schröter, Cathrin Weiß, Rahul Premraj, Thomas Zimmermann.
Proc. 2007 OOPSLA Workshop on Eclipse Technology eXchange (ETX), Montreal, Canada, October 2007.
[PDF]
Abstract.
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 responses among the 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.
Talks
Keep me posted
People
Impressum ● Datenschutzerklärung
<webmaster@st.cs.uni-saarland.de> · http://www.st.cs.uni-saarland.de//softevo/bugreports.php?lang=en · Stand: 2018-04-05 13:41
|
---|