Ticket Coverage：将测试覆盖率放入上下文
Ticket Coverage: Putting Test Coverage into Context
摘要：
没有一个度量标准可以确定一个票证的实现经过了多好的测试。因此，在票证上下文中更改的代码可能会无意中保持未测试状态并进入生产环境。这是一个主要问题，因为更改的代码比未更改的代码更容易出错。在本文中，我们引入了度量票覆盖率，把测试覆盖率的上下文门票。对于每个票证，它确定自动或手动测试所覆盖的更改方法的比例。我们进行了实证研究，由650K行Java代码的工业系统，并表明，门票覆盖率带来的透明度到门票的测试状态，并揭示了相关的测试差距。
英文摘要：
There is no metric that determines how well the implementation of a ticket has been tested. As a consequence, code changed within the context of a ticket might unintentionally remain untested and get into production. This is a major problem, because changed code is more fault-prone than unchanged code. In this paper, we introduce the metric ticket coverage which puts test coverage into the context of tickets. For each ticket, it determines the ratio of changed methods covered by automated or manual tests. We conducted an empirical study on an industrial system consisting of 650k lines of Java code and show that ticket coverage brings transparency into the test state of tickets and reveals relevant test gaps.
机构、总结、中文摘要均由AI分析而来，可能存在错误，请以论文正文为准。
