Abstract
Android has become the most popular OS because of its user-friendly environment, free-ware licensing and thousands of available applications. It is an open source for contributors and developers. The challenging problem in Android apps is to handle the bugs those are generated because of code segment (code constructs) written by developers to fix the reported bug. so code change management is also as critical task, as bug tracking. We have investigated all available previous history of Android bug reports and code changes to identify bug introducing changes. Apply the chi square test to observe the buggy construct. This study will help the reviewers, contributors, developers and quality assurance testers to concentrate and take special care while making or accepting changes to those constructs where it is most likely to induce a bug, which will lead to improve the quality of services provided by Android platform, and ultimately will get more satisfied user.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
References
Android/issues, fix, merged Androidreview. googlesource Code Review. Accessed 19 Jan 2016
Aversano, L., Cerulo, L., Grosso, C.D.: Learning from bug-introducing changes to prevent fault prone code. In: Ninth International Workshop on Principles of Software Evolution: in Conjunction with the 6th ESEC/FSE Joint Meeting, IWPSE 2007, p. 19 (2011)
Fiaz, A.S.S., Devi, N., Aarthi, S.: Bug tracking and reporting system, no. 1, pp. 42–45 (2012). Issues - Android - Android Open Source Project - Issue Tracker - Google Project Hosting
Kim, S., Zimmermann, T., Pan, K., Whitehead Jr., E.: Automatic identification of bug introducing changes. In: 21st IEEE/ACM International Conference on Automated Software Engineering (ASE 2006), pp. 81–90 (2006)
Lamkanfi, A., Perez, J., Demeyer, S.: The Eclipse and Mozilla defect tracking dataset: a genuine dataset for mining bug information. In: 2013 10th Working Conference on Mining Software Repositories, pp. 203–206 (2013)
Martie, L., Palepu, V.K., Sajnani, H., Lopes, C.: Trendy bugs topic trends in the Android bug reports, pp. 120–123 (2012)
Shihab, E., Kamei, Y., Bhattacharya, P.: Mining challenge 2012: the Android platform. In: 9th IEEE Working Conference on Mining Software Repositories, pp. 112–115 (2012)
Sinha, V.S., Mani, S., Gupta, M.: MINCE: mining change history of Android project. In: 2012 9th IEEE Working Conference on Mining Software Repositories (MSR), pp. 132–135 (2012)
Śliwerski, J., Zimmermann, T., Zeller, A.: When do changes induce fixes? ACM SIGSOFT Softw. Eng. Notes 30(4), 1 (2005)
Thung, F., Lo, D., Jiang, L.: Automatic recovery of root causes from bug-fixing changes. In: 20th Working Conference on Reverse Engineering, pp. 92–101 (2013)
Wang, D., Zhang, H., Liu, R., Lin, M., Wu, W.: Predicting bugs’ components via mining bug reports. J. Softw. 7(5), 1149–1154 (2012)
Whitehead, E.J.: Classifying software changes: clean or buggy? IEEE Trans. Softw. Eng. 34(2), 181–196 (2008)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2018 Springer Nature Singapore Pte Ltd.
About this paper
Cite this paper
Ramay, W.Y., Akbar, A., Sajjad, M. (2018). Bug Patterns Detection from Android Apps. In: Yuan, H., Geng, J., Liu, C., Bian, F., Surapunt, T. (eds) Geo-Spatial Knowledge and Intelligence. GSKI 2017. Communications in Computer and Information Science, vol 849. Springer, Singapore. https://doi.org/10.1007/978-981-13-0896-3_27
Download citation
DOI: https://doi.org/10.1007/978-981-13-0896-3_27
Published:
Publisher Name: Springer, Singapore
Print ISBN: 978-981-13-0895-6
Online ISBN: 978-981-13-0896-3
eBook Packages: Computer ScienceComputer Science (R0)