Each product directory contains for each bug attribute an XML file containing the corresponding information. Both Eclipse and Mozilla have a separate directory consisting of the products we previously selected. Structure of the DatasetĪs we see above, the Eclipse and Mozilla Defect Tracking Dataset is bundled as a set of XML files. With each report in the dataset, a list of modifications provides the full update history. an update of the current development state, e.g., the status of a bug report changes from new to assigned and subsequently to closed.a report provides inaccurate information.a report is incomplete and thus does not include vital information to fix the bug.There are several reasons why changing/updating the information of a reported bug is desirable: The information provided in a bug report can be modified during its lifetime. ProductĪs an end-user of software application reports a malfunctioning in a software application, the end-user provides contextual information concerning the observed bug. Below, we show the selected products along with some basic information for Eclipse and Mozilla respectively. The Eclipse and Mozilla Defect Tracking Dataset contains the bug reported for 4 popular products retrieved from both Eclipse and Mozilla. Below, you can find additional information about the dataset. Besides providing a single snapshot of a bug report, we also include all the incremental modifications as performed during the lifetime of the bug report. Welcome to the Mozilla and Eclipse Defect Tracking Dataset: a dataset with over 200.000 reported bugs extracted from the Eclipse and Mozilla projects (respectively 47.000 and 168.000 reported bugs). The Mozilla and Eclipse Defect Tracking Dataset
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |