An approach to detecting duplicate bug reports using natural language and execution information

By Xiaoyin Wang, Lu Zhang, Tao Xie, John Anvik, Jiasu Sun. 2008 ACM/IEEE 30th International Conference on Software Engineering, 2008

584 citations recorded by the source corpus.

Subfields: Information Systems, Signal Processing

View Paper: https://www.semanticscholar.org/paper/a18e5eecebd45c72edb4388ab2d9266de3f757c7

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Signal Processing

Citations in the corpus

Duplicate bug reports considered harmful … really? (2008, methodology): “To assist triagers, research proposed to use natural language processing [10] [17], sometimes combined with execution information [19].”
ReLink: recovering links between bugs and changes (2011, background): “Runeson et al. [26] and Wang et al. [30] applied IR techniques to compare text similarity between two bug reports, thereby identifying potentially duplicate bug reports.”
Predicting the severity of a reported bug (2010, methodology): “consider not only the actual bug reports, but also include “execution information” of a program which is for example the execution traces [5].”
Improving bug triage with bug tossing graphs (2009, methodology): “To detect duplicates, several approaches use natural language processing techniques on the bug description [18, 23], sometimes combined with runtime traces [27].”
A Hidden Markov Model to detect coded information islands in free text (2013, background): “[6]—different kinds of information such as natural language text and stack traces contribute to the approach accuracy.”
Automated severity assessment of software defect reports (2008, methodology): “[14], who proposed the recall rate as evaluation for their approach, also used in [18].”
It's not a bug, it's a feature: How misclassification impacts bug prediction (2013, background): “It is possible to automatically detect bug report duplicates [17], [18] that, when combined, might fill information gaps that prevent bug report fixes.”
Towards more accurate retrieval of duplicate bug reports (2011, methodology): “We extend BM25F model to better fit duplicate bug report detection problem by extending the original model to better fit longer queries.”
Is it a bug or an enhancement?: a text-based approach to classify change requests (2008, unknown): “[20] proposed an approach to assist triagers in detecting duplicate issues.”
A discriminative model approach for accurate duplicate bug report retrieval (2010, methodology): “In [22], Wang et al. extended the work by Runeson et al. in two dimensions.”
Where should the bugs be fixed? More accurate information retrieval-based bug localization based on bug reports (2012, background): “Many researchers mine bug report information to solve software engineering problems such as duplicate bug detection [33, 35], automatic bug triage [4, 7], bug report quality analysis [6, 7], and defect prediction [20, 37].”
A Survey on Automated Log Analysis for Reliability Engineering (2020, background): “e repository. These duplicate issue reports should be detected when new report arrives. Otherwise, issue maintainer will encounter heavy but unnecessary workload to process these reports. Wang et al. [140] uses classification techniques to detect duplicate issues with higher accuracy from informativ”
RCLinker: Automated Linking of Issue Reports and Commits Leveraging Rich Contextual Information (2015, unknown): “There also a number of techniques that infer missing links between duplicated bug reports [52], [59], [26], [55], [54], [58], [48], [1].”