JDT

<p><strong>Overview of Data</strong></p> <p>The data is present in 2 files:</p> <p>“JDT.xlsx” : A spreadsheet with the bug-ids, commits, its summary, files etc.</p> <p>“JDT.xml” : An xml file with more detailed information than the above spreadsheet(detailed files changed).</p> <p><strong>Attribute Information</strong></p> <p>The spreadsheet contains a table with the “bug_id”, “summary”, “description”, “time_reported”, “commit associated”, “status of commit” and “files committed”.</p> <p>The xml contains the above information and additionally the lines associated with the commit.</p> <p><strong>Paper Abstract</strong></p> <p>Bug localization refers to the automated process of locating the potential buggy files for a given bug report. To help developers focus their attention to those files is crucial. Several existing automated approaches for bug localization from a bug report face a key challenge, called lexical mismatch, in which the terms used in bug reports to describe a bug are different from the terms and code tokens used in source files. This paper presents a novel approach that uses deep neural network (DNN) in combination with rVSM, an information retrieval (IR) technique. rVSM collects the feature on the textual similarity between bug reports and source files. DNN is used to learn to relate the terms in bug reports to potentially different code tokens and terms in source files and documentation if they appear frequently enough in the pairs of reports and buggy files. Our empirical evaluation on real-world projects shows that DNN and IR complement well to each other to achieve higher bug localization accuracy than individual models. Importantly, our new model, HyLoc, with a combination of the features built from DNN, rVSM, and project’s bug-fixing history, achieves higher accuracy than the state-of-the-art IR and machine learning techniques. In half of the cases, it is correct with just a single suggested file. Two out of three cases, a correct buggy file is in the list of three suggested files.