Full coverage was very expensive and difficult to achieve, because we had to hand-inspect our code to determine which lines were and were not hit by the test.
完全的覆盖是非常昂贵的并且很难达到，因为我们必须要手工的检查我们的代码以确定哪一行代码没有被测试覆盖到。
Agile Coaches and Consultants frequently warn their clients that traditional measures such as Earned Value, Hours Worked, Lines of Code, Code Coverage for Tests are not well suited to Agile Projects.
敏捷教练和咨询顾问们经常警告他们的客户：传统的度量指标，诸如收益价值、工作小时数、代码行数，以及代码测试覆盖率等都不能与敏捷项目很好地吻合。
3 It's easy for graders to run the tests under Coverlipse and determine if there is 100% code coverage or not.
3对于评分者来说在Coverlipse下运行测试并决定是否有100%的代码覆盖率是十分容易的。
High coverage percentages alone do not ensure the quality of your code.
单独的高覆盖率并不能确保代码的质量。
Having trust in the tests is not about code coverage, is about trusting your team mates they will add tests for all the important things.
测试中有可信度并不是和代码覆盖率有关，而是相信团队成员，他们会为重要的事物增加测试。
First he concedes that getting high coverage in place for a legacy environment (one where the code does not have tests) does require a potentially high, long-term investment.
首先，他承认对遗留环境(代码没有测试)采取高覆盖率的确需要长期的高投入。
Perfect, 100 percent code coverage is not always attainable.
并不总是可以得到完美的、100%的代码覆盖率。
They may give you all the code coverage you need, but they might not give you all the system coverage you need.
尽管它可以提供您所需的全部代码，但它可能无法提供您所需的全部系统功能。
Coverage reports measure the coverage of the entire program and analyze which code has or has not been tested.
Coverage报告测量整个项目的覆盖率，并分析哪些代码已经被分析过了，哪些没有。
Quality assurance in SQLite is done using full-coverage testing, not by compiler warnings or other static code analysis tools.
SQLite使用全面覆盖的测试来保证质量，而不是依靠编译器警告或静态代码分析工具。
PureCoverage greatly simplified the task of inspecting code coverage, making it easy to identify which parts of the code had or had not tested.
PureCoverage很大程度的简化了检查代码覆盖率的任务，这使识别哪一部分的代码已经或者还没有被测试变得非常简单。
PureCoverage tracks code coverage, so you can identify gaps in your testing and areas of your program that the runtime analysis tools are not seeing.
PureCoverage追踪代码覆盖，因此您可以发现测试与运行时分析工具不能发现的鸿沟。
While code coverage is a quite good metric, it can be misleading. Even if your tests cover 100% of your code, they may not actually test each behavior correctly.
但是，代码覆盖率这个指标有时也会产生误导，因为即使全部的代码都被测试到了，也未必说明这些代码所得到的运行结果是正确的。
And when PureCoverage reports a high level of code coverage, you know you have not introduced new blocks of code without also adding automated tests to exercise them.
当PureCoverage报告高级别的代码覆盖时，您可以知道并没有引入新的代码块，因此不必增加自动测试。
Looks like you need code coverage tool, which analyzes your solution and shows which lines of code tested and which are not.
看起来你需要代码覆盖率工具，分析解决方案，显示这行代码测试，哪些不是。
The Performance Analyzer , Call Stack , Code Coverage , and Step Outcapabilities are not available.
在性能分析器，调用堆栈，代码覆盖率，加强在能力不详。
However, if you re-import this XML file and then merge it with additional code coverage data, only the statistics on line coverage are retained, not the statistics on block coverage.
不过，如果您重新汇入这个xml档，并将它与其他程序码涵盖范围资料合并，则只会保留程序码行涵盖范围的统计资料，而不会保留程序码区块涵盖范围的统计资料。
Importing XML data - If you import Code coverage data from an XML file, you can only see statistics for line coverage, not block coverage.
汇入xml资料：如果您从XML档案汇入程序码涵盖范围资料，则只会看到程序码行涵盖范围的统计资料，而非程序码区块涵盖范围的统计资料。
Importing XML data - If you import Code coverage data from an XML file, you can only see statistics for line coverage, not block coverage.
汇入xml资料：如果您从XML档案汇入程序码涵盖范围资料，则只会看到程序码行涵盖范围的统计资料，而非程序码区块涵盖范围的统计资料。
应用推荐