Locating source code to be fixed based on initial bug reports - A case study on the eclipse project

Phiradet Bangcharoensap, Akinori Ihara, Yasutaka Kamei, Ken Ichi Matsumoto

Research output: Chapter in Book/Report/Conference proceedingConference contribution

11 Citations (Scopus)

Abstract

In most software development, a Bug Tracking System is used to improve software quality. Based on bug reports managed by the bug tracking system, triagers who assign a bug to fixers and fixers need to pinpoint buggy files that should be fixed. However if triagers do not know the details of the buggy file, it is difficult to select an appropriate fixer. If fixers can identify the buggy files, they can fix the bug in a short time. In this paper, we propose a method to quickly locate the buggy file in a source code repository using 3 approaches, text mining, code mining, and change history mining to rank files that may be causing bugs. (1) The text mining approach ranks files based on the textual similarity between a bug report and source code. (2) The code mining approach ranks files based on prediction of the fault-prone module using source code product metrics. (3) The change history mining approach ranks files based on prediction of the fault-prone module using change process metrics. Using Eclipse platform project data, our proposed model gains around 20% in TOP1 prediction. This result means that the buggy files are ranked first in 20% of bug reports. Furthermore, bug reports that consist of a short description and many specific words easily identify and locate the buggy file.

Original languageEnglish
Title of host publicationProceedings - 2012 4th International Workshop on Empirical Software Engineering in Practice, IWESEP 2012
Pages10-15
Number of pages6
DOIs
Publication statusPublished - Dec 31 2012
Event2012 4th International Workshop on Empirical Software Engineering in Practice, IWESEP 2012 - Osaka, Japan
Duration: Oct 26 2012Oct 27 2012

Publication series

NameProceedings - 2012 4th International Workshop on Empirical Software Engineering in Practice, IWESEP 2012

Other

Other2012 4th International Workshop on Empirical Software Engineering in Practice, IWESEP 2012
CountryJapan
CityOsaka
Period10/26/1210/27/12

All Science Journal Classification (ASJC) codes

  • Software

Fingerprint Dive into the research topics of 'Locating source code to be fixed based on initial bug reports - A case study on the eclipse project'. Together they form a unique fingerprint.

Cite this