Residual test coverage monitoring
Residual test coverage monitoring
复制标题
剩余测试覆盖率监控
DOI：
10.1145/302405.302637
复制
发表时间：
1999
期刊：
影响因子：
--
通讯作者：
M. Young
中科院分区：
文献类型：
--
作者：
C. Pavlopoulou;M. Young
结构覆盖标准经常被用作测试彻底性的指标，但是很少能达到标准的完全满足。当一个软件产品以低于100%的覆盖率发布时，测试人员明确或隐含地假设满足剩余测试义务（剩余）的执行要么是不可行的，要么是很少发生的，以至于它们对质量的影响可以忽略不计。违反这一假设表明测试过程中存在缺陷。部署环境中的监视，即使是在beta测试阶段，通常也仅限于错误和健全性检查。在实际使用中监测测试覆盖率的剩余部分可以提供额外的有用信息，但除非其性能影响非常小，否则不太可能被用户接受。Java程序的残留测试覆盖监测的原型工具的经验表明，至少对于语句覆盖，简单的策略，删除所有的探针，除了那些对应于残留的覆盖测试减少执行开销到可接受的低水平。
Structural coverage criteria are often used as an indicator of the thoroughness of testing, but complete satisfaction of a criterion is seldom achieved. When a software product is released with less than 100% coverage, testers are explicitly or implicitly assuming that executions satisfying the remaining test obligations (the residue) are either infeasible or occur so rarely that they have negligible impact on quality. Violation of this assumption indicates shortcomings in the testing process. Monitoring in the deployed environment, even in the beta test phase, is typically limited to error and sanity checks. Monitoring the residue of test coverage in actual use can provide additional useful information, but it is unlikely to be accepted by users unless its performance impact is very small. Experience with a prototype tool for residual test coverage monitoring of Java programs suggests that, at least for statement coverage, the simple strategy of removing all probes except those corresponding to the residue of coverage testing reduces execution overhead to acceptably low levels.