Characterizing duplicate bugs: Perceptions of practitioners and an empirical analysis

buir.contributor.authorHanhan, Idil
buir.contributor.authorTüzün, Eray
buir.contributor.orcidHanhan, Idil|0000-0002-5636-5637
buir.contributor.orcidTüzün, Eray|0000-0002-5550-7816
dc.citation.epagee2446-25en_US
dc.citation.issueNumberSpecial Issueen_US
dc.citation.spagee2446-1en_US
dc.contributor.authorKüçük, B.
dc.contributor.authorHanhan, Idil
dc.contributor.authorTüzün, Eray
dc.date.accessioned2023-02-15T06:26:50Z
dc.date.available2023-02-15T06:26:50Z
dc.date.issued2022-01-22
dc.departmentDepartment of Computer Engineeringen_US
dc.description.abstractBug handling is an essential part of the software development process. Ideally, in a bug-tracking system, bugs are reported, fixed, verified, and closed. In some cases, bugs have to be reopened mostly due to an incorrect fix. However, instead of reopening the existing bug report, users may submit a new report for a previously reported bug, which results in duplicate bug reports. Users might report duplicate bugs if they miss the previous bug report or if the previous bug is unresolved (i.e., in progress) and therefore cannot be reopened. These duplicate bug reports may cost extra maintenance efforts in triaging and bug fixing. There have been several studies on characterizing reopened bugs and duplicate bug reports; however, to the best of our knowledge, there has been no prior work on understanding the dynamics of their interaction, which is missed reopen bugs. Our study is based on analyzing the difference between duplicate and nonduplicate bugs and further categorizing the duplicate bugs. In this regard, we categorize duplicate bugs according to the original bug's resolution status at the duplicate's creation time as Master-Unresolved bugs and Master-Resolved (Missed Reopen) bugs to distinguish their properties. We compare these two types of bugs in terms of their relationship to their master bug, bug surface time, bug fix time, bug's severity, and the number of users involved. We perform case studies using the Eclipse and Mozilla projects' bug repositories that include more than 165,500 and 394,000 bug reports, respectively. Additionally, we investigate the perceived importance, impact, and causes of duplicate bugs, as well as the difference between nonduplicate and duplicate bugs and its categories for practitioners in the software industry by conducting a survey.en_US
dc.identifier.doi10.1002/smr.2446en_US
dc.identifier.eissn2047-7481
dc.identifier.issn2047-7473
dc.identifier.urihttp://hdl.handle.net/11693/111285
dc.language.isoEnglishen_US
dc.publisherWileyen_US
dc.relation.isversionofhttps://doi.org/10.1002/smr.2446en_US
dc.source.titleJournal of Software: Evolution and Processen_US
dc.subjectBug managementen_US
dc.subjectBug reopenen_US
dc.subjectCharacterization studyen_US
dc.subjectDuplicate bug reportsen_US
dc.subjectReopened bugsen_US
dc.titleCharacterizing duplicate bugs: Perceptions of practitioners and an empirical analysisen_US
dc.typeArticleen_US
Files
Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Characterizing_duplicate_bugs_Perceptions_of_practitioners_and_an_empirical_analysis.pdf
Size:
3.33 MB
Format:
Adobe Portable Document Format
Description:
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.69 KB
Format:
Item-specific license agreed upon to submission
Description: