Now, don't get me wrong: There's nothing foolish about using test coverage tools.
现在，不要误解我的意思：并不是说使用测试覆盖工具是愚蠢的。
Knowing this, developers, managers, and QA professionals can use test coverage tools where they really count — namely for three common scenarios.
知道这些以后，开发人员、管理人员以及QA专业人员就可以在真正需要的地方使用测试覆盖工具。
I'll say it one more time: you can (and should) use test coverage tools as part of your testing process, but don't be fooled by the coverage report.
我不止一次地说：您可以(而且应该)使用测试覆盖工具作为您的测试过程的一部分。但是不要被覆盖报告所愚弄。
Test coverage tools are generally easy to add into an established unit testing process, and the results can be reassuring.
测试覆盖工具通常可以很容易地添加到确定的单元测试过程中，而且结果可靠。
Test coverage tools modify your code to leave behind a trail of "bread crumbs" during execution (hence the names of the tools I'm targeting in this column).
测试覆盖工具旨在修改代码，使之在执行期间留下一条“面包屑”踪迹（这也是我在这一期关注的工具的名称由来）。
Test coverage tools modify your code to leave behind a trail of "bread crumbs" during execution (hence the names of the tools I'm targeting in this column).
测试覆盖工具旨在修改代码，使之在执行期间留下一条“面包屑”踪迹（这也是我在这一期关注的工具的名称由来）。
应用推荐