Papers
Topics
Authors
Recent
Gemini 2.5 Flash
Gemini 2.5 Flash
119 tokens/sec
GPT-4o
56 tokens/sec
Gemini 2.5 Pro Pro
43 tokens/sec
o3 Pro
6 tokens/sec
GPT-4.1 Pro
47 tokens/sec
DeepSeek R1 via Azure Pro
28 tokens/sec
2000 character limit reached

Toward Rapid Bug Resolution for Android Apps (2312.15318v1)

Published 23 Dec 2023 in cs.SE and cs.IR

Abstract: Bug reports document unexpected behaviors in software, enabling developers to understand, validate, and fix bugs. Unfortunately, a significant portion of bug reports is of low quality, which poses challenges for developers in terms of addressing these issues. Prior research has delved into the information needed for documenting high-quality bug reports and expediting bug report management. Furthermore, researchers have explored the challenges associated with bug report management and proposed various automated techniques. Nevertheless, these techniques exhibit several limitations, including a lexical gap between developers and reporters, difficulties in bug reproduction, and identifying bug locations. Therefore, there is a pressing need for additional efforts to effectively manage bug reports and enhance the quality of both desktop and mobile applications. In this paper, we describe the existing limitations of bug reports and identify potential strategies for addressing them. Our vision encompasses a future where the alleviation of these limitations and successful execution of our proposed new research directions can benefit both reporters and developers, ultimately making the entire software maintenance faster.

Definition Search Book Streamline Icon: https://streamlinehq.com
References (35)
  1. 2023. Apache Lucene- https://lucene.apache.org.
  2. 2023. BugZilla Issue Tracker - https://bugzilla.mozilla.org.
  3. 2023. ChatGPT- https://chat.openai.com.
  4. 2023. GitHub Issue Tracker - https://github.com/features.
  5. 2023. JIRA Bug Reporting System - https://www.atlassian.com/software/jira.
  6. 2023. Llama- https://ai.meta.com/llama/.
  7. 2023. An open letter to GitHub from the maintainers of open source projects. https://github.com/dear-github/dear-github.
  8. 2023. Prompt Engineering - https://platform.openai.com/docs/guides/prompt-engineering.
  9. What Makes a Good Bug Report?. In Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering (Atlanta, Georgia) (SIGSOFT ’08/FSE-16). Association for Computing Machinery, New York, NY, USA, 308–318. https://doi.org/10.1145/1453101.1453146
  10. Assessing the Quality of the Steps to Reproduce in Bug Reports. In Proceedings of the 2019 27th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering (Tallinn, Estonia) (ESEC/FSE 2019). Association for Computing Machinery, New York, NY, USA, 86–96.
  11. Detecting Missing Information in Bug Descriptions. In Proceedings of the 11th Joint Meeting on the Foundations of Software Engineering (ESEC/FSE’17). 396–407.
  12. Robert N. Charette. 2005. Why Software Fails. IEEE Spectrum (2005), 42–49.
  13. Palm: Scaling language modeling with pathways. arXiv preprint arXiv:2204.02311 (2022).
  14. Using bug report similarity to enhance bug localisation. In 2012 19th Working Conference on Reverse Engineering. IEEE, 125–134.
  15. Feature location in source code: a taxonomy and survey. Journal of software: Evolution and Process 25, 1 (2013), 53–95.
  16. Sidong Feng and Chunyang Chen. 2023. Prompting Is All You Need: Automated Android Bug Replay with Large Language Models. https://api.semanticscholar.org/CorpusID:259950715
  17. UniXcoder: Unified Cross-Modal Pre-training for Code Representation. arXiv preprint arXiv:2203.03850 (2022).
  18. An Empirical Investigation into the Reproduction of Bug Reports for Android Apps. 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) (2022).
  19. Amy J. Ko and Brad A. Myers. 2008. Debugging Reinvented: Asking and Answering Why and Why Not Questions about Program Behavior. In Proceedings of the 30th International Conference on Software Engineering (Leipzig, Germany) (ICSE ’08). Association for Computing Machinery, New York, NY, USA, 301–310. https://doi.org/10.1145/1368088.1368130
  20. On Using GUI Interaction Data to Improve Text Retrieval-based Bug Localization. ArXiv abs/2310.08083 (2023). https://api.semanticscholar.org/CorpusID:263909147
  21. Qualitative data analysis: a methods sourcebook. Thousand Oaks, Califorinia: SAGE Publications, Inc., [2014] ©2014.
  22. Auto-completing Bug Reports for Android Applications. In Proceedings of the Joint Meeting on Foundations of Software Engineering (FSE’15). 673–686.
  23. An Empirical Investigation into the Use of Image Captioning for Automated Software Documentation. In 2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER). 514–525. https://doi.org/10.1109/SANER53432.2022.00069
  24. The design of bug fixes. In 2013 35th International Conference on Software Engineering (ICSE). IEEE, 332–341.
  25. Mohammad Masudur Rahman and Chanchal K. Roy. 2018. Improving IR-Based Bug Localization with Context-Aware Query Reformulation. In Proceedings of the 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering (Lake Buena Vista, FL, USA) (ESEC/FSE 2018). Association for Computing Machinery, New York, NY, USA, 621–632.
  26. Nils Reimers and Iryna Gurevych. 2019. Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks. In Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing. Association for Computational Linguistics. http://arxiv.org/abs/1908.10084
  27. Yang Song and Oscar Chaparro. 2020. Bee: A tool for structuring and analyzing bug reports. In Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering. 1551–1555.
  28. BURT: A Chatbot for Interactive Bug Reporting. In 2023 IEEE/ACM 45th International Conference on Software Engineering (ICSE’23)). 170–174.
  29. Toward interactive bug reporting for (android app) end-users. In Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering. 344–356.
  30. How long will it take to fix this bug?. In Fourth International Workshop on Mining Software Repositories (MSR’07: ICSE Workshops 2007). IEEE, 1–1.
  31. Locus: Locating bugs from software changes. In Proceedings of the 31st International Conference on Automated Software Engineering (ASE’16). 262–273.
  32. Andror2: A Dataset of Manually-Reproduced Bug Reports for Android apps. 2021 IEEE/ACM 18th International Conference on Mining Software Repositories (MSR) (2021), 600–604.
  33. Improved bug localization based on code change histories and bug reports. Information and Software Technology 82 (2017), 177–192.
  34. Where Should the Bugs Be Fixed? More Accurate Information Retrieval-Based Bug Localization Based on Bug Reports. In Proceedings of the International Conference on Software Engineering (ICSE’12). 14–24.
  35. What Makes a Good Bug Report? IEEE Transactions on Software Engineering 36, 5 (2010), 618–643.
User Edit Pencil Streamline Icon: https://streamlinehq.com
Authors (1)
  1. Junayed Mahmud (10 papers)

Summary

We haven't generated a summary for this paper yet.

Ai Sparkles Streamline Icon: https://streamlinehq.com Summarize Now