Bug Patterns Detection from Android Apps

  • Waheed Yousuf RamayEmail author
  • Arslan Akbar
  • Muhammad Sajjad
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 849)


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.


BD (Bug Detection) SCM (Software Coding Management) AOS (Android Open Source Apps) 


  1. 1.
    Android/issues, fix, merged Androidreview. googlesource Code Review. Accessed 19 Jan 2016Google Scholar
  2. 2.
    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)Google Scholar
  3. 3.
    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 HostingGoogle Scholar
  4. 4.
    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)Google Scholar
  5. 5.
    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)Google Scholar
  6. 6.
    Martie, L., Palepu, V.K., Sajnani, H., Lopes, C.: Trendy bugs topic trends in the Android bug reports, pp. 120–123 (2012)Google Scholar
  7. 7.
    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)Google Scholar
  8. 8.
    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)Google Scholar
  9. 9.
    Śliwerski, J., Zimmermann, T., Zeller, A.: When do changes induce fixes? ACM SIGSOFT Softw. Eng. Notes 30(4), 1 (2005)CrossRefGoogle Scholar
  10. 10.
    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)Google Scholar
  11. 11.
    Wang, D., Zhang, H., Liu, R., Lin, M., Wu, W.: Predicting bugs’ components via mining bug reports. J. Softw. 7(5), 1149–1154 (2012)Google Scholar
  12. 12.
    Whitehead, E.J.: Classifying software changes: clean or buggy? IEEE Trans. Softw. Eng. 34(2), 181–196 (2008)CrossRefGoogle Scholar

Copyright information

© Springer Nature Singapore Pte Ltd. 2018

Authors and Affiliations

  • Waheed Yousuf Ramay
    • 1
    Email author
  • Arslan Akbar
    • 1
  • Muhammad Sajjad
    • 2
  1. 1.School of Computer and Communication EngineeringUniversity of Science and Technology BeijingBeijingChina
  2. 2.Department of Computer ScienceGovernment Degree CollegeSahiwalPakistan

Personalised recommendations