Empirical software engineering at Microsoft Research
Proceedings of the ACM 2011 conference on Computer supported cooperative work
Towards systematic analysis of continuous user input
Proceedings of the 4th international workshop on Social software engineering
The inductive software engineering manifesto: principles for industrial data mining
Proceedings of the International Workshop on Machine Learning Technologies in Software Engineering
Developer prioritization in bug repositories
Proceedings of the 34th International Conference on Software Engineering
Content classification of development emails
Proceedings of the 34th International Conference on Software Engineering
BugRedux: reproducing field failures for in-house debugging
Proceedings of the 34th International Conference on Software Engineering
FastFix: monitoring control for remote software maintenance
Proceedings of the 34th International Conference on Software Engineering
Learning to classify bug reports into components
TOOLS'12 Proceedings of the 50th international conference on Objects, Models, Components, Patterns
How do software engineers understand code changes?: an exploratory study in industry
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Towards understanding software change request assignment: a survey with practitioners
Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
F3: fault localization for field failures
Proceedings of the 2013 International Symposium on Software Testing and Analysis
User involvement in software evolution practice: a case study
Proceedings of the 2013 International Conference on Software Engineering
Reproducing and debugging field failures in house
Proceedings of the 2013 International Conference on Software Engineering
Proceedings of the 10th Working Conference on Mining Software Repositories
Communication in open source software development mailing lists
Proceedings of the 10th Working Conference on Mining Software Repositories
Interactive record/replay for web application debugging
Proceedings of the 26th annual ACM symposium on User interface software and technology
Hi-index | 0.00 |
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.