Search

Your search keyword '"Fix recommendation"' showing total 3 results
Start Over Descriptor "Fix recommendation"
3 results on '"Fix recommendation"'

1. Ammonia: an approach for deriving project-specific bug patterns.

Author

Higo, Yoshiki, Hayashi, Shinpei, Hata, Hideaki, and Nagappan, Meiyappan

Subjects
AMMONIA, SOFTWARE engineering, COMPUTER software developers, COMPUTER software, COMPUTER programming
Abstract

Finding and fixing buggy code is an important and cost-intensive maintenance task, and static analysis (SA) is one of the methods developers use to perform it. SA tools warn developers about potential bugs by scanning their source code for commonly occurring bug patterns, thus giving those developers opportunities to fix the warnings (potential bugs) before they release the software. Typically, SA tools scan for general bug patterns that are common to any software project (such as null pointer dereference), and not for project specific patterns. However, past research has pointed to this lack of customizability as a severe limiting issue in SA. Accordingly, in this paper, we propose an approach called Ammonia, which is based on statically analyzing changes across the development history of a project, as a means to identify project-specific bug patterns. Furthermore, the bug patterns identified by our tool do not relate to just one developer or one specific commit, they reflect the project as a whole and compliment the warnings from other SA tools that identify general bug patterns. Herein, we report on the application of our implemented tool and approach to four Java projects: Ant, Camel, POI, and Wicket. The results obtained show that our tool could detect 19 project specific bug patterns across those four projects. Next, through manual analysis, we determined that six of those change patterns were actual bugs and submitted pull requests based on those bug patterns. As a result, five of the pull requests were merged. [ABSTRACT FROM AUTHOR]

Published
2020
Full Text
View/download PDF

2. Ammonia: an approach for deriving project-specific bug patterns

Author

Higo, Yoshiki, Hayashi, Shinpei, Hata, Hideaki, Nagappan, Meiyappan, Higo, Yoshiki, Hayashi, Shinpei, Hata, Hideaki, and Nagappan, Meiyappan

Abstract

Finding and fixing buggy code is an important and cost-intensive maintenance task, and static analysis (SA) is one of the methods developers use to perform it. SA tools warn developers about potential bugs by scanning their source code for commonly occurring bug patterns, thus giving those developers opportunities to fix the warnings (potential bugs) before they release the software. Typically, SA tools scan for general bug patterns that are common to any software project (such as null pointer dereference), and not for project specific patterns. However, past research has pointed to this lack of customizability as a severe limiting issue in SA. Accordingly, in this paper, we propose an approach called Ammonia, which is based on statically analyzing changes across the development history of a project, as a means to identify project-specific bug patterns. Furthermore, the bug patterns identified by our tool do not relate to just one developer or one specific commit, they reflect the project as a whole and compliment the warnings from other SA tools that identify general bug patterns. Herein, we report on the application of our implemented tool and approach to four Java projects: Ant, Camel, POI, and Wicket. The results obtained show that our tool could detect 19 project specific bug patterns across those four projects. Next, through manual analysis, we determined that six of those change patterns were actual bugs and submitted pull requests based on those bug patterns. As a result, five of the pull requests were merged.

Published
2023

3. Ammonia experimental results on four projects (Ant, Camel, POI, Wicket)

Author

Yoshiki Higo

Subjects
Change Patterns, Fix Recommendation, Project-Specific Bug Patterns, Mining Software Repositories, Pattern Mining
Abstract

This is a package of our experimental materials of our paper submitted to EMSE journal. This package includes a jar file of Ammonia, which is an implementation of our proposed technique, and the followings for each target software. 1. a cloned git repository of the target software 2. a database including change patterns derived from the repository 3. a shell-script to launch our tool Ammonia in UNIX/MAC environment 4. a bat-file to launch Ammonia in Windows environment To launch Ammonia, just run shell-script or bat-file without arguments. The following are expected time that Ammonia's Window will launch. Ant: 10 seconds Camel: 2 minutes and 30 seconds POI: 20 seconds Wicket: 1 minute and 30 seconds After the Ammonia's Window shows up, please do the following operations, 1. Input "1" to the text field of "UPPER LIMIT OF MATCHED NUMBER" and push the enter key. 2. Click "EXC" and input "/test" to the text field of "WORDS FOR FILTERING" and push the enter key. After the both 1. and 2. operations are done, "FILE LIST" shows only the latent buggy code that we analyzed in the experiment.

Published
2019
Full Text
View/download PDF

Catalog

Books, media, physical & digital resources
See catalog results