TY - GEN
T1 - Do Visual Issue Reports Help Developers Fix Bugs?
T2 - 30th IEEE/ACM International Conference on Program Comprehension, ICPC 2022
AU - Kuramoto, Hiroki
AU - Kondo, Masanari
AU - Kashiwa, Yutaro
AU - Ishimoto, Yuta
AU - Shindo, Kaze
AU - Kamei, Yasutaka
AU - Ubayashi, Naoyasu
N1 - Funding Information:
This research was partially supported by JSPS KAKENHI Japan (Grant Numbers: JP18H04097, 21H04877, 21K17725) and JSPS International Joint Research Program with SNSF (Project “SENSOR”: JPJSJRP20191502).
Publisher Copyright:
© 2022 ACM.
PY - 2022
Y1 - 2022
N2 - Issue reports are a pivotal interface between developers and users for receiving information about bugs in their products. In practice, issue reports often have incorrect information or insufficient information to enable bugs to be reproduced, and this has the effect of delaying the entire bug-fixing process. To facilitate their bug-reproduction work, GitHub has provided a new feature that allows users to share videos (e.g., mp4 files.) Using such videos, reports can be made to developers about the details of bugs by recording the symptoms, reproduction steps, and other important aspects of bug information. While such visual issue reports have the potential to significantly improve the bug-fixing process, no studies have empirically exam-ined this impact. In this paper, we conduct a preliminary study to identify the characteristics of visual issue reports by comparing them with non-visual issue reports. We collect 1,230 videos and 18,760 images from 226,286 issues on 4,173 publicly available repositories. Our preliminary analysis shows that issue reports with images are described in fewer words than non-visual issue reports. In addition, we observe that most dis-cussions in visual issue reports are concerned with either conditions for reproduction (e.g., when) or GUI (e.g., pageviewcontroller.)
AB - Issue reports are a pivotal interface between developers and users for receiving information about bugs in their products. In practice, issue reports often have incorrect information or insufficient information to enable bugs to be reproduced, and this has the effect of delaying the entire bug-fixing process. To facilitate their bug-reproduction work, GitHub has provided a new feature that allows users to share videos (e.g., mp4 files.) Using such videos, reports can be made to developers about the details of bugs by recording the symptoms, reproduction steps, and other important aspects of bug information. While such visual issue reports have the potential to significantly improve the bug-fixing process, no studies have empirically exam-ined this impact. In this paper, we conduct a preliminary study to identify the characteristics of visual issue reports by comparing them with non-visual issue reports. We collect 1,230 videos and 18,760 images from 226,286 issues on 4,173 publicly available repositories. Our preliminary analysis shows that issue reports with images are described in fewer words than non-visual issue reports. In addition, we observe that most dis-cussions in visual issue reports are concerned with either conditions for reproduction (e.g., when) or GUI (e.g., pageviewcontroller.)
UR - http://www.scopus.com/inward/record.url?scp=85133187812&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85133187812&partnerID=8YFLogxK
U2 - 10.1145/3524610.3527882
DO - 10.1145/3524610.3527882
M3 - Conference contribution
AN - SCOPUS:85133187812
T3 - IEEE International Conference on Program Comprehension
SP - 511
EP - 515
BT - Proceedings - 30th IEEE/ACM International Conference on Program Comprehension, ICPC 2022
PB - IEEE Computer Society
Y2 - 16 May 2022 through 17 May 2022
ER -