Get started
Keyword

bug reports

Description: Bug reports are descriptions of software errors or flaws, used in software development to document, investigate, and resolve defects.
Wikidata ID: wiki/Q138457958
OpenAlex ID: keywords/bug-reports
Finding and understanding bugs in C compilers
2011 · Xuejun Yang, Yang Chen, et al. · Proceedings of the ACM SIGPLAN Conference on Programming Language Design and Implementation · 825
What makes a good bug report?
2008 · Nicolas Bettenburg, Sascha Just, et al. · ACM SIGSOFT International Symposium on Foundations of Software Engineering (FSE) · 621
Finding and understanding bugs in C compilers
2011 · Xuejun Yang, Yang Chen, et al. · ACM SIGPLAN Notices · 587
User feedback in the appstore: An empirical study
2013 · Dennis Pagano, Walid Maalej · IEEE International Requirements Engineering Conference (RE) · 560
Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports
2012 · Jian Zhou, Hongyu Zhang, et al. · Proceedings/Proceedings - International Conference on Software Engineering · 507
How can i improve my app? Classifying user reviews for software maintenance and evolution
2015 · Sebastiano Panichella, Andrea Di Sorbo, et al. · IEEE International Conference on Software Maintenance and Evolution (ICSME) · 473
PDF
Bug report, feature request, or simply praise? On automatically classifying app reviews
2015 · Walid Maalej, Hadeer Nabil · IEEE International Requirements Engineering Conference (RE) · 463
It's not a bug, it's a feature: How misclassification impacts bug prediction
2013 · Kim Herzig, Sascha Just, et al. · Proceedings/Proceedings - International Conference on Software Engineering · 444
ReLink
2011 · Rongxin Wu, Hongyu Zhang, et al. · 411
Automatic bug triage using text categorization.
2004 · Davor Čubranić, Gail C. Murphy · 407
Improving bug localization using structured information retrieval
2013 · Ripon K. Saha, Matthew Lease, et al. · IEEE/ACM International Conference on Automated Software Engineering (ASE) · 401
How Long Will It Take to Fix This Bug?
2007 · Cathrin Weiss, Rahul Premraj, et al. · 377
Where should the bugs be fixed? - more accurate information retrieval-based bug localization based on bug reports
2012 · Jian Zhou, Hongyu Zhang, et al. · 372
Latent Dirichlet Allocation
2015 · Joshua Charles Campbell, Abram Hindle, et al. · Elsevier eBooks · 349
Predicting the severity of a reported bug
2010 · Ahmed Lamkanfi, Serge Demeyer, et al. · 349
PDF
Modeling bug report quality
2007 · Pieter Hooimeijer, Westley Weimer · 320
On the automatic classification of app reviews
2016 · Walid Maalej, Zijad Kurtanović, et al. · Requirements Engineering · 280
Characterizing and predicting which bugs get fixed
2010 · Philip J. Guo, Thomas Zimmermann, et al. · 266
Version history, similar report, and structure: putting them together for improved bug localization
2014 · Shaowei Wang, David Lo · International Conference on Program Comprehension · 222
Execution synthesis
2010 · Cristian Zamfir, George Candea · European Conference on Computer Systems · 222
PDF
On the use of deep learning in software defect prediction
2022 · Görkem Giray, Kwabena Ebo Bennin, et al. · Journal of Systems and Software · 212
PDF
Boosting Bug-Report-Oriented Fault Localization with Segmentation and Stack-Trace Analysis
2014 · Chu-Pan Wong, Yingfei Xiong, et al. · IEEE International Conference on Software Maintenance and Evolution (ICSME) · 212
Sentiment Polarity Detection for Software Development
2017 · Fabio Calefato, Filippo Lanubile, et al. · Empirical Software Engineering · 211
PDF
Do developers feel emotions? an exploratory analysis of emotions in software artifacts
2014 · Alessandro Murgia, Parastou Tourani, et al. · Working Conference on Mining Software Repositories (MSR) · 208
Information needs in bug reports
2010 · Silvia Breu, Rahul Premraj, et al. · ACM Conference on Computer Supported Cooperative Work (CSCW) · 204
Works count: 2,562
Citation count: 38,750
Year
Topic
Type