Mapping Bug Reports to Relevant Files and Automated Bug Assigning to the Developer

Authors

  • Alphy Jose  Computer Science and Engineering, Mar Athanasius College of Engineering and Technology, Ernakulam, Kerala, India
  • Aby Abahai T  Computer Science and Engineering, Mar Athanasius College of Engineering and Technology, Ernakulam, Kerala, India

Keywords:

Bug Report, Bug mapping, Bug triaging.

Abstract

Then bug means the coding mistake that occurs in the software developing stage. It may occurs because of many reasons and some of the reasons are version mismatch, network incompatibility, and unavailability of supporting documents. And bug report means a user level description about a bug. A bug report mainly having a bug id, summery about a bug and a detailed description about the bug. A tool for ranking all the source files with respect to how likely they are to contain the cause of the bug would enable developers to narrow down their search and improve productivity. The ranking is done on the basis of comparing the source code and the bug report, here 19 features are considering for the bug mapping procedure. And bug triaging refers to the process of assigning a bug to the most appropriate developer in order to fix the bug. The process of bug triaging is based on the interest of the developer and the bug mapping history of each developer. And also avoiding the chances of occurrence of duplication in repository. This method is very useful for java projects working in the netbeans, eclipse, tomcat platforms.

References

  1. R. Saha, M. Lease, S. Khurshid, and D. Perry, "Improving bug localization using structured information retrieval," in Proc. IEEE/ACM 28th Int. Conf. Autom. Softw. Eng., Nov. 2013, pp. 345-355. [2]
  2. J. Zhou, H. Zhang, and D. Lo, "Where should the bugs be fixed? -more accurate information retrieval-based bug localization based on bug reports," in Proc. Int. Conf. Softw. Eng., Piscataway, NJ, USA, 2012 pp. 14-24.
  3. Xin Ye, "Mapping Bug Reports to Relevant Files: A Ranking Model, a Fine Grained Benchmark, and Feature Evaluation" IEEE Trans. Softw. Eng., Vol. 42, No. 4, pp. 379-402, April. 2016.
  4. http://www.nltk.org/api/nltk.stem.html.
  5. G. Antoniol and Y.-G. Gueheneuc, "Feature identification: A novel approach and a case study," in Proc. 21st IEEE Int. Conf. Softw. Maintenance,Washington, DC, USA, 2005, pp. 357- 366.
  6. G. Antoniol and Y.-G. Gueheneuc, "Feature identification: An epidemiological metaphor," IEEE Trans. Softw. Eng., vol. 32, no. 9, pp. 627-641, Sep. 2006.
  7. B. Ashok, J. Joy, H. Liang, S. K. Rajamani, G. Srinivasa, and V. Vangala, "Debugadvisor: A recommender system for debugging," in Proc. 7th Joint Meeting Eur. Softw. Eng. Conf. ACM SIGSOFT Symp. Found. Softw. Eng., New York, NY, USA, 2009, pp. 373-382.
  8. A. Bacchelli and C. Bird, "Expectations, outcomes, and challenges of modern code review," in Proc. Int. Conf. Softw. Eng., Piscataway, NJ, USA, 2013, pp. 712-721.
  9. S. K. Bajracharya, J. Ossher, and C. V. Lopes, "Leveraging usage similarity for effective retrieval of examples in code repositories," in Proc. 18th ACM SIGSOFT Int. Symp. Found. Softw. Eng., New York, NY, USA, 2010 pp. 157-166.
  10. R. M. Bell, T. J. Ostrand, and E. J. Weyuker, "Looking for bugs in all the right places," in Proc. Int. Symp. Softw. Testing Anal., New York, NY, USA, 2006, pp. 61-72.

IInternational Journal of Scientific Research in Computer Science, Engineering and Information Technology

Downloads

Published

2018-02-28

Issue

Volume 3, Issue 1, January-February-2018

Section

Research Articles

License

Copyright (c) IJSRCSEIT

Creative Commons License

This work is licensed under a Creative Commons Attribution 4.0 International License.

How to Cite

[1]
Alphy Jose, Aby Abahai T, " Mapping Bug Reports to Relevant Files and Automated Bug Assigning to the Developer, IInternational Journal of Scientific Research in Computer Science, Engineering and Information Technology(IJSRCSEIT), ISSN : 2456-3307, Volume 3, Issue 1, pp.1290-1295, January-February-2018.