scholarly journals An Empirical Analysis of Bug Reports and Bug Fixing in Open Source Android Apps

2013 ◽  
Author(s):  
P. Bhattacharya ◽  
L. Ulanova ◽  
I. Neamtiu ◽  
S. C. Koduru
Keyword(s):  
Open Source ◽  
Empirical Analysis ◽  
Android Apps ◽  
Bug Reports ◽  
Bug Fixing

A Commit Messages-Based Bug Localization for Android Applications

2019 ◽  
Vol 29 (04) ◽  
pp. 457-487 ◽  
Author(s):  
Tao Zhang ◽  
Wenjun Hu ◽  
Xiapu Luo ◽  
Xiaobo Ma
Keyword(s):  
Open Source ◽  
Software Maintenance ◽  
State Of The Art ◽  
Bug Localization ◽  
Two Phase ◽  
Android Apps ◽  
Bug Reports ◽  
Android Applications ◽  
The Given ◽  
General Method

Recently, there has been consistent growth in Android applications (apps). Under these circumstances, software maintenance for Android apps becomes an essential and important task. The core of software maintenance is to locate bugs in source files. Previous bug localization approaches mainly focus on open-source desktop software (e.g. Eclipse, Mozilla, GCC). Even though a few studies locate the bugs in the Android apps, they are dedicated to a special app named ZXing, without developing a general method to locate the bugs in Android apps by taking into account the unique characteristics of Android apps’ bug reports. Such characteristics include fewer number of historical bug reports, insufficient detailed description, etc. These characteristics hinder existing localization approaches from being directly delivered to Android apps, because lack of enough information degrades the performance of those localization approaches relying on historical bug reports. Commit messages include more informative data which can provide the details of reported bugs. Therefore, in this paper, we propose a novel information retrieval-based approach which utilizes commit messages to locate new bugs in Android apps. This approach not only considers the structured textual similarity between the given bug and the candidate source files, but also computes the unstructured textual similarities between the new bug and the commit messages linked to the corresponding source files. According to the experimental results on 10 popular open-source Android apps managed by GitHub, our approach outperforms the state-of-the-art bug localization methods that include BugLocator, BLUiR, and two-phase model.

scholarly journals UNDERSTANDING THE DEVELOPER PARTICIPATION IN BUG FIX PROCESS

2014 ◽  
Vol 12 (8) ◽  
pp. 3823-3828
Author(s):  
Madhu Kumari ◽  
Meera Sharma ◽  
Nikita Yadav
Keyword(s):  
Linear Relationship ◽  
Open Source ◽  
Significant Variation ◽  
Open Source Project ◽  
Bug Reports ◽  
Bug Fixing ◽  
Bug Report ◽  
Severity Class ◽  
Software Bug

Prediction of the bug fix time in open source softwares is a challenging job. A software bug consists of many attributes that define the characteristics of the bug. Some of the attributes get filled at the time of reporting and some are  at the time of bug fixing. In this paper, 836 bug reports of two products namely Thunderbird and Webtools of Mozilla open source project have been considered. In  bug report, we see that there is no linear relationship among the bug attributes namely bug fix time, developers, cc count and severity. This paper has analyzed the interdependence among these attributes through graphical representation.The results conclude that :Case 1. 73% of bugs reported for Webtools are fixed by 17% developers and 61% of bugs are fixed by 14% developers for Thundebird.Case 2. We tried to find a relationship between the time taken by a developer in fixing a bug and the corresponding developer. We also observed that there is a significant variation in bug fixing process, bugs may take 1 day to 4 years in fixing.Case 3. There is no linear relationship between cc count i.e. manpower involved in bug fixing process and bug fix time.Case 4. Maximum number of developers are involved in fixing bugs for major severity class.

Mining Bug Report Repositories to Identify Significant Information for Software Bug Fixing

2021 ◽  
Author(s):  
Bancha Luaphol ◽  
Jantima Polpinij ◽  
Manasawee Kaenampornpan
Keyword(s):  
The Other ◽  
Problem Domain ◽  
Significant Information ◽  
Bug Reports ◽  
Bug Fixing ◽  
Classification Technique ◽  
Bug Report ◽  
Multiple Issues ◽  
Improved Accuracy ◽  
Software Bug

Most studies relating to bug reports aims to automatically identify necessary information from bug reports for software bug fixing. Unfortunately, the study of bug reports focuses only on one issue, but more complete and comprehensive software bug fixing would be facilitated by assessing multiple issues concurrently. This becomes a challenge in this study, where it aims to present a method of identifying bug reports at severe level from a bug report repository, together with assembling their related bug reports to visualize the overall picture of a software problem domain. The proposed method is called “mining bug report repositories”. Two techniques of text mining are applied as the main mechanisms in this method. First, classification is applied for identifying severe bug reports, called “bug severity classification”, while “threshold-based similarity analysis” is then applied to assemble bug reports that are related to a bug report at severe level. Our datasets are from three opensource namely SeaMonkey, Firefox, and Core:Layout downloaded from the Bugzilla. Finally, the best models from the proposed method are selected and compared with two baseline methods. For identifying severe bug reports using classification technique, the results show that our method improved accuracy, F1, and AUC scores over the baseline by 11.39, 11.63, and 19% respectively. Meanwhile, for assembling related bug reports using threshold-based similarity technique, the results show that our method improved precision, and likelihood scores over the other baseline by 15.76, and 9.14% respectively. This demonstrate that our proposed method may help increasing chance to fix bugs completely.

Is Bug Severity in Line with Bug Fixing Change Complexity?

2020 ◽  
Vol 30 (11n12) ◽  
pp. 1779-1800
Author(s):  
Zengyang Li ◽  
Peng Liang ◽  
Dengwei Li ◽  
Ran Mo ◽  
Bing Li
Keyword(s):  
Effort Estimation ◽  
Severity Level ◽  
Release Planning ◽  
Bug Reports ◽  
Bug Fixing ◽  
Code Change ◽  
Study Results ◽  
Significant Difference ◽  
Lower Severity ◽  
Severity Levels

Both complexity of code change for bug fixing and bug severity play an important role in release planning when considering which bugs should be fixed in a specific release under certain constraints. This work investigates whether there are significant differences between bugs of different severity levels regarding the complexity of code change for fixing the bugs. Code change complexity is measured by the number of modified lines of code, source files, and packages, as well as the entropy of code change. We performed a case study on 20 Apache open source software (OSS) projects using commit records and bug reports. The study results show that (1) for bugs of high severity levels (i.e. Blocker, Critical and Major in JIRA), there is no significant difference on the complexity of code change for fixing bugs of different severity levels for most projects, while (2) for bugs of low severity levels (i.e. Major, Minor and Trivial in JIRA), fixing bugs of a higher severity level needs significantly more complex code change than fixing bugs of a lower severity level for most projects. These findings provide useful and practical insights for effort estimation and release planning of OSS development.

Tool Assisted Analysis of Open Source Projects

2011 ◽  
Vol 3 (2) ◽  
pp. 43-78 ◽  
Author(s):  
M.M. Mahbubul Syeed ◽  
Timo Aaltonen ◽  
Imed Hammouda ◽  
Tarja Systä
Keyword(s):  
Cloud Computing ◽  
Open Source ◽  
Open Source Software ◽  
Community Structures ◽  
Support Tool ◽  
Bug Fixing ◽  
Code Base ◽  
Formal Definitions ◽  
Assisted Analysis ◽  
Query Operations

Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. OSS code adoption requires an understanding of the structure of the code base. For a deeper understanding of the maintenance, bug fixing and development activities, the structure of the developer community also needs to be understood, especially the relations between the code and community structures. This, in turn, is essential for the development and maintenance of software containing OSS code. This paper proposes a method and support tool for exploring the relations of the code base and community structures of OSS projects. The method and proposed tool, Binoculars, rely on generic and reusable query operations, formal definitions of which are given in the paper. The authors demonstrate the applicability of Binoculars with two examples. The authors analyze a well-known and active open source project, FFMpeg, and the open source version of the IaaS cloud computing project Eucalyptus.

From Android Bug Reports to Android Bug Handling Process

2016 ◽  
Vol 7 (4) ◽  
pp. 1-18
Author(s):  
Liguo Yu
Keyword(s):  
Project Management ◽  
Open Source ◽  
Tracking System ◽  
Software Project ◽  
Bug Reports ◽  
Bug Report ◽  
Bug Tracking ◽  
Android Development ◽  
Comprehensive Study

Android is an operating system for mobile devices. Its development is led by Google and some other companies. Because of the open-source property of Android, anyone can report a bug through its online bug tracking system. In this paper, we analyze the bug reports of Android operating systems. Specifically, through this study, we would like to answer the following questions regarding Android development and its project management: (1) Could Android bug reports be handled on time? (2) What is the distribution of different maintenance activities initiated by Android bug reports? (3) How long does it take to handle an Android bug report? (4) Are the number of followers and the number of following messages of an Android bug report related to the effort spent on handling this bug report? Through answering these questions, this paper presents a comprehensive study of Android bug reporting and handling process. The information and knowledge obtained through this case study could help us better understand open-source software project, such as its development process and project management.

An Empirical Analysis of Software Changes on Statement Entity in Java Open Source Projects

2012 ◽  
Vol 4 (2) ◽  
pp. 16-31 ◽  
Author(s):  
Xiaoyan Zhu ◽  
Qinbao Song ◽  
Zhongbin Sun
Keyword(s):  
Open Source ◽  
Empirical Analysis ◽  
Software Projects ◽  
Software Changes

Software projects keep changing all the time. Understanding the nature of the changes can help build higher quality projects. In this paper, the authors studied software changes on a new entity, statement. They found some types of statements are more likely to change than others. Furthermore, the authors studied software changes to fix bugs and also found some types of statements are more likely to change than others to fix bugs. These statements are more likely to cause bugs, which should be paid more attention to.

Sign in / Sign up

Export Citation Format

Share Document