What Makes a Good Bug Report?
What Makes a Good Bug Report?
复制标题
DOI：
10.1145/1453101.1453146
复制
发表时间：
2008-11
影响因子：
7.4
通讯作者：
Thomas Zimmermann;Rahul Premraj;Nicolas Bettenburg;Sascha Just;Adrian Schröter;Cathrin Weiss
中科院分区：
文献类型：
--
作者：
Thomas Zimmermann;Rahul Premraj;Nicolas Bettenburg;Sascha Just;Adrian Schröter;Cathrin Weiss
在软件开发中，错误报告为开发人员提供了重要的信息。但是，这些报告的质量差异很大。我们对Apache，Eclipse和Mozilla的开发人员和用户进行了一项调查，以找出是什么是一个好的错误报告。对466个响应的分析揭示了开发人员需要的信息与用户提供的信息之间的信息不匹配。大多数开发人员将复制，堆叠痕迹和测试用例的步骤视为有用，同时最难为用户提供。这种洞察力有助于设计新的错误跟踪工具，以指导用户收集并提供更多有用的信息。我们的Cuezilla原型是这样的工具，可以衡量新错误报告的质量；它还建议添加哪些元素以提高质量。我们培训了Cuezilla的289个错误报告样本，并由开发人员评为调查的一部分。我们调查的参与者还提供了175条有关报告和解决错误的障碍的评论。基于这些评论，我们讨论了一些有关更好的错误跟踪系统的建议，这些建议应该集中于吸引错误记者，更好的工具支持以及改进的错误重复处理。
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 for designing 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. The participants of our survey also provided 175 comments on hurdles in reporting and resolving bugs. Based on these comments, we discuss several recommendations for better bug tracking systems, which should focus on engaging bug reporters, better tool support, and improved handling of bug duplicates.