Web Application Interface Data Collector for Issue Reporting

Volume 9, Issue 5, Page No 01-08, 2024

Author’s Name: Diego Costa, Gabriel Matos, Anderson Lins, Leon Barroso, Carlos Aguiar, Erick Bezerra

View Affiliations

SIDIA Institute of Science and Technology, Manaus, Brazil

^a)whom correspondence should be addressed. E-mail: die go.costa@sidia.com

Adv. Sci. Technol. Eng. Syst. J. 9(5), 01-08 (2024); DOI: 10.25046/aj090501

Keywords: Bug Reporting, Software Management, Web Application, Browser API

Download Now!

63 Downloads

Export Citations

Abstract

Insufficient information is often pointed out as one of the main problems with bug reports as most bugs are reported manually, they lack detailed information describing steps to reproduce the unexpected behavior, leading to increased time and effort for developers to reproduce and fix bugs. Current bug reporting systems lack support for self-hosted systems that cannot access third-party cloud environments or Application Programming Interfaces due to confidentiality concerns. To address this, we propose Watson, a Typescript framework with a minimalist User Interface developed in Vue.js. The objectives are to minimize the user’s effort to report bugs, simplify the bug reporting process, and provide relevant information for developers to solve it. Watson was designed to capture user’s interactions, network logs, screen recording, and seamlessly integration with issue tracker systems in self-hosted systems that cannot share their data to external Application Programming Interfaces or cloud services. Watson also can be installed via Node Package Manager and integrated into most JavaScript or TypeScript web projects. To evaluate Watson, we developed an Angular-based application along with two usage scenarios. First, the users experimented the application without using Watson and once they found a bug, they reported it manually on GitLab. Later, they used the same application, but this time, whenever they detect another bug, they reported it through Watson User Interface. Watson, as stated by the experiment participants and the evidences, is useful and helpful for development teams to report issues and provide relevant information for tracking bugs. The identification of bug root causes was almost three times more effective with Watson than manual reporting.

Received: 24 April 2024 Revised: 01 August 2024 Accepted: 03 August 2024 Online: 14 September 2024

Full Text

References (21)

Matos, D. Costa, A. Lins, E. Bezerra, L. Barroso, C. Aguiar, T. Ferraz, I. Teixeira, “Watson: Web Application Interface Data Collector for Feed- back Reporting,” in 2023 IEEE 30th Annual Software Technology Conference (STC), 3–6, 2023, doi:1109/STC58598.2023.00007.
Song, O. Chaparro, “Bee: A tool for structuring and analyzing bug reports,” in Proceedings of the 28th ACM Joint Meeting on European Software Engineer- ing Conference and Symposium on the Foundations of Software Engineering, 1551–1555, 2020, doi:10.1145/3368089.3417928.
Moran, “Enhancing android application bug reporting,” in Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering, 1045– 1047, 2015, doi:10.1145/2786805.2807557.
Erfani Joorabchi, M. Mirzaaghaei, A. Mesbah, “Works for me! characterizing non-reproducible bug reports,” in Proceedings of the 11th working conference on mining software repositories, 62–71, 2014, doi:10.1145/2597073.2597098.
Soltani, F. Hermans, T. Ba¨ck, “The significance of bug report elements,” Empirical Software Engineering, 25, 5255–5294, 2020, doi:10.1007/s10664- 020-09882-z.
Zimmermann, R. Premraj, N. Bettenburg, S. Just, A. Schroter, C. Weiss, “What makes a good bug report?” IEEE Transactions on Software Engineering, 36(5), 618–643, 2010, doi:10.1109/TSE.2010.63.
Huo, T. Ding, C. McMillan, M. Gethers, “An empirical study of the effects of expert knowledge on bug reports,” in 2014 IEEE International Conference on Software Maintenance and Evolution, 1–10, IEEE, 2014, doi:10.1109/ICSME.2014.22.
Wang, M. Li, S. Wang, T. Menzies, Q. Wang, “Images don’t lie: Duplicate crowdtesting reports detection with screenshot information,” Information and Software Technology, 110, 139–155, 2019, doi:10.1016/j.infsof.2019.03.003.
Cooper, C. Bernal-Ca´rdenas, O. Chaparro, K. Moran, D. Poshyvanyk, “It Takes Two to Tango: Combining Visual and Textual Information for Detecting Duplicate Video-Based Bug Reports,” in 2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE), 957–969, 2021, doi:10.1109/ICSE43902.2021.00091.
Bheree, J. Anvik, “Identifying and Detecting Inaccurate Stack Traces in Bug Reports,” in 2024 7th International Conference on Software and System Engineering (ICoSSE), 9–14, IEEE Computer Society, Los Alamitos, CA, USA, 2024, doi:10.1109/ICoSSE62619.2024.00010.
Noyori, H. Washizaki, Y. Fukazawa, K. Ooshima, H. Kanuka, S. No- jiri, “Deep learning and gradient-based extraction of bug report features re- lated to bug fixing time,” Frontiers in Computer Science, 5, 1032440, 2023, doi:10.3389/fcomp.2023.1032440.
Krasniqi, H. Do, “A multi-model framework for semantically enhancing detection of quality-related bug report descriptions,” Empirical Software Engi- neering, 28(2), 42, 2023, doi:10.1007/s10664-022-10280-w.
Sharma, A. Dagur, R. Chaturvedi, et al., “Automated bug reporting system in web applications,” in 2018 2nd International Conference on Trends in Electronics and Informatics (ICOEI), 1484–1488, IEEE, 2018, doi:10.1109/ICOEI.2018.8553850.
Chaparro, C. Bernal-Ca´rdenas, J. Lu, K. Moran, A. Marcus, M. Di Penta, D. Poshyvanyk, V. Ng, “Assessing the quality of the steps to reproduce in bug reports,” in Proceedings of the 2019 27th ACM Joint Meeting on Euro- pean Software Engineering Conference and Symposium on the Foundations of Software Engineering, 86–96, 2019, doi:10.1145/3338906.3338947.
Moran, M. Linares-Va´squez, C. Bernal-Ca´rdenas, C. Vendome, D. Poshy- vanyk, “Automatically discovering, reporting and reproducing android applica- tion crashes,” in 2016 IEEE international conference on software testing, verifi- cation and validation (icst), 33–44, IEEE, 2016, doi:10.1109/ICST.2016.34.
Song, J. Mahmud, Y. Zhou, O. Chaparro, K. Moran, A. Marcus, D. Poshy- vanyk, “Toward interactive bug reporting for (android app) end-users,” in Proceedings of the 30th ACM Joint European Software Engineering Confer- ence and Symposium on the Foundations of Software Engineering, 344–356, 2022, doi:10.1145/3540250.3549131.
Grano, A. Ciurumelea, S. Panichella, F. Palomba, H. C. Gall, “Exploring the integration of user feedback in automated testing of Android applications,” in 2018 IEEE 25th International Conference on Software Analysis, Evolution and Reengineering (SANER), 72–83, 2018, doi:10.1109/SANER.2018.8330198.
Feng, C. Chen, “Prompting Is All You Need: Automated Android Bug Replay with Large Language Models,” in Proceedings of the 46th IEEE/ACM International Conference on Software Engineering, 1–13, 2024, doi:10.1145/3597503.3608137.
Burg, R. Bailey, A. J. Ko, M. D. Ernst, “Interactive record/replay for web application debugging,” in Proceedings of the 26th annual ACM symposium on User interface software and technology, 473–484, 2013, doi:10.1145/2501988.2502050.
Hibschman, H. Zhang, “Unravel: Rapid web application reverse engineering via interaction recording, source tracing, and library detection,” in Proceedings of the 28th Annual ACM Symposium on User Interface Software & Technology, 270–279, 2015, doi:10.1145/2807442.2807468.
Johnson, J. Mahmud, T. Wendland, K. Moran, J. Rubin, M. Fazz- ini, “An Empirical Investigation into the Reproduction of Bug Reports for Android Apps,” in 2022 IEEE International Conference on Soft- ware Analysis, Evolution and Reengineering (SANER), 321–322, 2022, doi:10.1109/SANER53432.2022.00048.

Web Application Interface Data Collector for Issue Reporting