Code coverage is a way of seeing how much code is covered by a set of tests 工具对测试进行度量。代码覆盖是一种查看一套测试覆盖了多少代码的方法。
This means that there should not be any unnecessary overlap or gaps in the test coverage 这意味着，在测试覆盖中，不应当有任何不必要的覆盖或缺口。
Test coverage measurement tools are a fantastic addition to the unit testing paradigm 对单元测试范例而言，测试覆盖度量工具是一个有点奇怪的组成部分。
This type of approach lets you control the amount of test coverage you want , from zero to all test cases 这种方法允许控制希望的测试覆盖数量，可以从0个到所有测试用例。
By default , particular colors are used to indicate whether code was covered by tests that have been run 默认情况下，将使用特定的颜色来指示代码是否被已运行的测试覆盖了。
I ll say it one more time : you can and should use test coverage tools as part of your testing process , but 我不止一次地说：您可以（而且应该）使用测试覆盖工具作为您的测试过程的一部分。但是
In any case , the master test plan needs to ensure that the st and at are complementary with regard to test coverage 无论如何，主测试计划需要确保，系统测试和验收测试是有关测试覆盖的补充。
Test coverage tools are generally easy to add into an established unit testing process , and the results can be reassuring 测试覆盖工具通常可以很容易地添加到确定的单元测试过程中，而且结果可靠。
When i run the test coverage process again with the new test cases , i get a much more complete report , as shown in figure 2 当我使用新的测试案例再次执行测试覆盖过程时，我得到了如图2所示的更加完整的报告。
Knowing this , developers , managers , and qa professionals can use test coverage tools where they really count - namely for three common scenarios 知道这些以后，开发人员、管理人员以及qa专业人员就可以在真正需要的地方使用测试覆盖工具。
