In this work, we study how the authorship of code affects bug-fixing commits using the SStuBs dataset, a collection of single-statement bug fix changes in popular Java Maven projects. More specifically, we study the differences in characteristics between simple bug fixes by the original author -- that is, the developer who submitted the bug-inducing commit -- and by different developers (i.e., non-authors). Our study shows that nearly half (i.e., 44.3%) of simple bugs are fixed by a different developer. We found that bug fixes by the original author and by different developers differed qualitatively and quantitatively. We observed that bug-fixing time by authors is much shorter than that of other developers. We also found that bug-fixing commits by authors tended to be larger in size and scope, and address multiple issues, whereas bug-fixing commits by other developers tended to be smaller and more focused on the bug itself. Future research can further study the different patterns in bug-fixing and create more tailored tools based on the developer's needs.
翻译:在这项工作中,我们研究代码的作者如何影响对错误的修补。 使用 SStuBs 数据集, 收集流行的 Java Maven 项目中的单一声明错误修补修改。 更具体地说, 我们研究原始作者 -- -- 即提交诱虫操作的开发者 -- -- 和不同的开发者( 即非作者)之间简单的错误修补方法的特性差异。 我们的研究显示, 近一半( 即 44. 3% ) 的简单错误修补方法是由不同的开发者固定的。 我们发现, 原始作者和不同的开发者对错误的修补方法在质量上和数量上有所不同。 我们发现, 作者对错误修补时间比其他开发者的时间要短得多。 我们还发现, 作者对错误的修补方法在规模和范围上往往要大, 并解决多种问题。 而其他开发者对错误修补方法的修补往往较小, 并且更侧重于错误本身。 未来的研究可以进一步研究错误修补方法的不同模式, 并根据开发者的需求创建更适合的工具。