这里是一些稍微抽象的测试用例被分成更详细的测试步骤的地方，这些步骤将变成测试脚本（要么是人工生成，要么自动生成）。
This is where somewhat abstract test cases are developed into more detailed test steps, which in turn will become test scripts (either manual or automated).
在随后的计划中，您可以通过向每一个测试用例添加一个加权值，来提供一份详细的关于测试执行效果的估计。
Later in the plan, you can provide a more detailed estimate of the test execution effort by adding a weight value to each test case.
测试和QA计划：详细说明测试和 QA 计划，并在其中包括测试用例。
Testing and QA plan: Details the testing and QA plans and includes test cases.
我们前面提到，创建测试用例的详细信息比较费力，并需要大量使用SDO编程API。
We mentioned earlier that the creation of the details of the test case is somewhat laborious, requiring extensive use of the SDO programming APIs.
测试用例的范畴，像标签那样，让您能够为更详细的报告将测试用例拆分。
Test case categories, which, like tags, enable you to partition your test cases for more detailed reporting.
有关性能改进和获得这些数值时使用的测试用例的更详细的信息，请参阅performancereportsfor WebSphereMessageBrokerV6。
For further details on the performance improvement and test cases used for these figures, see the performance reports for WebSphere Message Broker V6.
测试用例列出了哪些指定项目是需要被测试的，以及怎样去验证软件的详细步骤。
Test cases list the specific items that will be tested and describe the detailed steps that will be followed to verify the software.
详细探讨了面向对象单元测试、面向对象集成测试和面向对象系统测试的测试策略，以及相应的测试用例设计方法。
Testing strategies of object-oriented unit test, object-oriented integrate test, object-oriented system test and their designing approach of testing data were discussed in detail.
它提供了一种机制，使测试可以报告一般测试的某些部分的详细结果。例如，如果一般测试用于运行多个第三方测试用例，则通过该机制可以得到每个测试用例的结果。
It provides a mechanism that lets your test report detailed results for portions of the generic test, such as per-test-case results if the generic test is used to run multiple third-party test cases.
然后，可以添加测试用例的详细信息，如下图所示。
You can then add the details for your test case, as shown in the following illustration.
然后，可以添加测试用例的详细信息，如下图所示。
You can then add the details for your test case, as shown in the following illustration.
应用推荐