Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

Developers' Perception: Fixed Bugs Often Overlooked as Quality Contributions

Vitaly Alifanov, Kamil Almetov, Ivan Kornienko, Arsen Mutalapov, Yegor Bugayenko

TL;DR

Through a survey of 102 programmers, it is discovered that only a third of them perceive the quantity of bugs found and rectified in a repository as indicative of higher quality, substantiating the notion that programmers often misinterpret the significance of testing and bug reporting.

Abstract

High-quality software products rely on both well-written source code and timely detection and thorough reporting of bugs. However, some programmers view bug reports as negative assessments of their work, leading them to withhold reporting bugs, thereby detrimentally impacting projects. Through a survey of 102 programmers, we discovered that only a third of them perceive the quantity of bugs found and rectified in a repository as indicative of higher quality. This finding substantiates the notion that programmers often misinterpret the significance of testing and bug reporting.

Developers' Perception: Fixed Bugs Often Overlooked as Quality Contributions

TL;DR

Through a survey of 102 programmers, it is discovered that only a third of them perceive the quantity of bugs found and rectified in a repository as indicative of higher quality, substantiating the notion that programmers often misinterpret the significance of testing and bug reporting.

Abstract

High-quality software products rely on both well-written source code and timely detection and thorough reporting of bugs. However, some programmers view bug reports as negative assessments of their work, leading them to withhold reporting bugs, thereby detrimentally impacting projects. Through a survey of 102 programmers, we discovered that only a third of them perceive the quantity of bugs found and rectified in a repository as indicative of higher quality. This finding substantiates the notion that programmers often misinterpret the significance of testing and bug reporting.
Paper Structure (8 sections, 1 figure, 7 tables)

This paper contains 8 sections, 1 figure, 7 tables.

Table of Contents

  1. Introduction
  2. Related Work
  3. Method
  4. Results
  5. RQ1: Do programmers consider software quality being positively correlated with the number of bugs reported?
  6. RQ2: Do programmers feel comfortable when they report bugs?
  7. Discussion
  8. Conclusion

Figures (1)

  • Figure 1: This is the bug report about some authentication problems. Respondents were asked to choose a few options out of six: what would they do in order to improve this report?