Filling the Gaps of Development Logs and Bug Issue Data

Romo, Bilyaminu Auwal; Capiluppi, Andrea; Hall, Tracy

doi:10.1145/2641580.2641592

Cited by 10 publications

(9 citation statements)

References 10 publications

(10 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The objective is to replicate an initial, exploratory analysis performed on one OSS project [10] with a larger dataset, and to quantify the issue of traceability of issue tracker bugs into development logs. In order to detect the bug fixing activity, we used a subset of the SZZ algorithm [12]; and two data mining tools, the Bicho issue tracker parser [6], and the CVSAnalY development log parser [9].…”

Section: Introductionmentioning

confidence: 99%

Towards an automation of the traceability of bugs from development logs

Romo

Capiluppi

2015

Proceedings of the 19th International Conference on Evaluation and Assessment in Software Engineering

Self Cite

View full text Add to dashboard Cite

Context: Information and tracking of defects can be severely incomplete in almost every Open Source project, resulting in a reduced traceability of defects into the development logs (i.e., version control commit logs). In particular, defect data often appears not in sync when considering what developers logged as their actions. Synchronizing or completing the missing data of the bug repositories, with the logs detailing the actions of developers, would benefit various branches of empirical software engineering research: prediction of software faults, software reliability, traceability, software quality, effort and cost estimation, bug prediction and bug fixing.Objective: To design a framework that automates the process of synchronizing and filling the gaps of the development logs and bug issue data for open source software projects.Method: We instantiate the framework with a sample of OSS projects from GitHub, and by parsing, linking and filling the gaps found in their bug issue data, and development logs. UML diagrams show the relevant modules that will be used to merge, link and connect the bug issue data with the development data.Results: Analysing a sample of over 300 OSS projects we observed that around 1/2 of bug-related data is present in either development logs or issue tracker logs: the rest of the data is missing from one or the other source. We designed an automated approach that fills the gaps of either source by making use of the available data, and we successfully mapped all the missing data of the analysed projects, when using one heuristics of annotating bugs. Other heuristics need to be investigated and implemented.

show abstract

Section: Introductionmentioning

confidence: 99%

Towards an automation of the traceability of bugs from development logs

Romo

Capiluppi

2015

Proceedings of the 19th International Conference on Evaluation and Assessment in Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…The ID of this bug should return the development information in Figure 1. Corresponding fields linked in Bicho and CVSAnalY adapted from [17] SCMlog referring to the actual #3507 bug in the BT system. Instead, the information refers to a request to merge some changes in the distributed VC system.…”

Section: A Identifying Bugs In Development Logs and Bt Datamentioning

confidence: 99%

“…Instead, the information refers to a request to merge some changes in the distributed VC system. We marked these occurrences as 'false positives' and excluded them from the pilot study as well as the extended study [17], [16].…”

Section: A Identifying Bugs In Development Logs and Bt Datamentioning

confidence: 99%

“…Traceability links are needed to perform various software evolutionary activities, for instance to design and build defect prediction models [21]. However, the available tools to document development logs lack integration [7] with the bug tracking systems: thus, two independent sets of bug-related data are produced, filling different databases [17]. It has been suggested that using the bug IDs from development logs could help to identify and recover missing traceability links [10] [13] [2].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Locating Bug IDs and Development Logs in Open Source Software (OSS) projects: An Experience Report

Romo

Capiluppi

Ali

2018

2018 International Conference on Innovation and Intelligence for Informatics, Computing, and Technologies (3ICT)

Self Cite

View full text Add to dashboard Cite

The development logs of software projects, contained in Version Control (VC) systems can be severely incomplete when tracking bugs, especially in open source projects, resulting in a reduced traceability of defects. Other times, such logs can contain bug information that is not available in bug tracking system (BT system) repositories, and vice-versa: if development logs and BT system data were used together, researchers and practitioners often would have a larger set of bug IDs for a software project, and a better picture of a bug life cycle, its evolution and maintenance. Considering a sample of 10 OSS projects and their development logs and BT systems data, the two objectives of this paper are (i) to determine which of the keywords 'Fix', 'Bug' or the '#' identifier provide the better precision; and (ii) to analyse their respective precision and recall at locating the larger amount possible of bug IDs manually. Overall, our results suggest that the use of the '#' identifier in conjunction with the bug ID digits (e.g., #1234) is more precise for locating bugs in development logs, than the use of the 'Bug' and 'Fix' keywords. Such keywords are indeed present in the development logs, but they are less useful when trying to connect the development actions with the bug traces in software project.

show abstract

“…However, sometimes developers violate guidelines and commit changes without issue reference [2], [3]. For this reason, various research studies investigated possible ways to recover missing links (e.g., [2], [4], [5]).…”

Section: Introductionmentioning

confidence: 99%

Discovering Loners and Phantoms in Commit and Issue Data

Schermann

Brandtner

Panichella

et al. 2015

2015 IEEE 23rd International Conference on Program Comprehension

View full text Add to dashboard Cite

The interlinking of commit and issue data has become a de-facto standard in software development. Modern issue tracking systems, such as JIRA, automatically interlink commits and issues by the extraction of identifiers (e.g., issue key) from commit messages. However, the conventions for the use of interlinking methodologies vary between software projects. For example, some projects enforce the use of identifiers for every commit while others have less restrictive conventions. In this work, we introduce a model called PaLiMod to enable the analysis of interlinking characteristics in commit and issue data. We surveyed 15 Apache projects to investigate differences and commonalities between linked and non-linked commits and issues. Based on the gathered information, we created a set of heuristics to interlink the residual of non-linked commits and issues. We present the characteristics of Loners and Phantoms in commit and issue data. The results of our evaluation indicate that the proposed PaLiMod model and heuristics enable an automatic interlinking and can indeed reduce the residual of non-linked commits and issues in software projects. Abstract-The interlinking of commit and issue data has become a de-facto standard in software development. Modern issue tracking systems, such as JIRA, automatically interlink commits and issues by the extraction of identifiers (e.g., issue key) from commit messages. However, the conventions for the use of interlinking methodologies vary between software projects. For example, some projects enforce the use of identifiers for every commit while others have less restrictive conventions. In this work, we introduce a model called PaLiMod to enable the analysis of interlinking characteristics in commit and issue data. We surveyed 15 Apache projects to investigate differences and commonalities between linked and non-linked commits and issues. Based on the gathered information, we created a set of heuristics to interlink the residual of non-linked commits and issues. We present the characteristics of Loners and Phantoms in commit and issue data. The results of our evaluation indicate that the proposed PaLiMod model and heuristics enable an automatic interlinking and can indeed reduce the residual of non-linked commits and issues in software projects.

show abstract

Filling the Gaps of Development Logs and Bug Issue Data

Cited by 10 publications

References 10 publications

Towards an automation of the traceability of bugs from development logs

Towards an automation of the traceability of bugs from development logs

Locating Bug IDs and Development Logs in Open Source Software (OSS) projects: An Experience Report

Discovering Loners and Phantoms in Commit and Issue Data

Contact Info

Product

Resources

About