A step by step example of building a registry utility, with test cases.
一步步教你建立一个存取Registry的工具及其测试案例。
After you import the test scripts, you can associate them with test cases.
在导入测试脚本之后，您可以将其与测试用例联系起来。
The test cases defined can then only be tested by combining them with test cases.
然后这些定义的测试用例只能通过将它们与测试用例合并来测试。
You must associate your automated tests with test cases and add them to a test suite in a test plan.
您必须建立自动化测试与测试案例的关联，并将它们加入到测试计划中的测试套件。
In this case the tree looks different: you start with test cases, and then trace back from scenarios and use cases.
在此种情况下，追踪树看起来会有不同：你从测试用例开始，然后追踪场景和用例。
The test plan is automatically populated with test cases linked to each of the requirements in the collection, as Figure 13 shows.
测试计划会自动填充与收集中每一个需求相链接的测试用例，如图 13 所示。
With test cases and the percentage mix, the test team can now execute the scripts. To achieve reasonable test results, a test should include.
有了测试用例和百分比组合，测试团队现在就可以执行脚本了。
If your defect and test repository is managed on the same server as ClearQuest, you will be able to work with test cases and defect reports within the same client.
如果您的缺陷和测试储存库在同一个服务器上被管理，如ClearQuest，那么您将能够在同一个客户端中与测试用例和缺陷报告一起工作。
Regardless of how it happens, after you have entered the requirements, you can associate them with test cases to trace your test scripts all the way back to your requirements.
不论什么情况，当您进入了需求之后，您可以将它们与测试用例相关联，从而将测试脚本一直追溯到您的需求。
Using this technique, the tester does not start with a set of test cases or any other pre-defined testing script.
使用这个技术，测试人员不必以一系列测试用例开始，也不用其它预定义的测试脚本。
Working with test developers to implement the plan and execute the use cases.
与测试开发人员一起实施计划和执行用例。
Sequence diagram test cases visualize how the system under test should be interacting with other instances over time.
序列图测试用例显示了，测试之下的系统可以与其他的实例相交流。
With our three test cases set up, we can now look at some different types of test results.
对我们的三个测试都进行了设置，现在我们能够看到一些不同的测试结果类型。
With every change, there is a regression library of test cases that needs to be executed to ensure stability.
对于每个变更，都有需要确保稳定性而执行的测试用例的回归库。
Test cases with requirements that change or are deleted are identified as questionable.
与改变或者删除需求一起的测试用例，会作为合理的进行标示。
Test plans, test cases, and configured test cases can all be tagged with one or more iterations.
测试计划、测试用例、以及被配置的测试用例都能够被一个或者多个迭代进行标记。
When you do this, the tree view is immediately populated with specific configured versions of the test cases.
当您执行这些操作时，树形视图将会立即被加载上测试用例特定的被配置的版本。
A test script can then be associated with the configured test cases.
测试脚本就会与已配置测试用例联合起来。
You might have orphan test logs, such as those with parent test cases that have been deleted.
您可能只有测试日志，例如那些删除的上级测试用例。
Compare the templates in Listing 2 with the test cases in Listing 3 and you will find a one-to-one match.
比较清单2中的模板和清单3中的测试条件，就会发现存在一一对应的关系。
As with other appropriate pairs of requirements and test cases, an analyst previously has noted (with a facility called traceability) that this requirement and this test case are related.
由于有其它适当的成对的需求与测试用例，分析师之前并已经注意到(通过被叫作可追踪性)这个需求与这个测试用例是有联系的。
Note that two different workloads were used in this test (with and without report use cases).
注意该测试中用到了两种不同的工作负荷(有和没有报告用例)。
To run all the test cases, we set up a server with the following specifications.
为了运行所有测试案例，我们组装一台具有以下规格的服务器。
With end-use UIs, develop test cases that validate what these users can do against the new solution vs. what they are allowed to do in the supporting applications
利用使用端 UI，开发出的测试案例可验证这些用户依靠新解决方案能做些什么，以及配套应用程序允许他们做些什么。
This information allows the user to both launch DeviceAnywhere from the ClearQuest interface and associate ClearQuest-configured test cases with DeviceAnywhere scripts.
这些信息让用户可以从ClearQuest界面启动DeviceAnywhere，并且将由ClearQuest配置的测试用例与deviceanywhere脚本关联起来。
Because JUnit itself decorates all test cases with a setUp and a tearDown method, execution times must be considered within the overall context of a test scenario.
由于JUnit本身用一个setUp和一个tearDown方法装饰所有测试样例，所以要在测试场景的整个上下文中考虑执行时间。
Create and manage test cases and associate them with the test plan.
创建并管理测试用例，并将它们与测试计划联系起来。
You can run the test cases with rake, or you can run the test cases individually.
可以用rake运行测试用例，也可以单独运行每个测试用例。
If test cases that were run before will need to be rerun for this iteration, just tag these test cases with the new iteration to identify them as Planned.
如果测试用例在此之前已经运行过的话，那么需要在这次迭代中重新被运行，只需将这些测试用例标注为Planned用以识别它们。
The associations between elements (such as test cases with a test plan) have to be added manually.
元素之间的联系（例如一个测试用例与测试规划之间的联系）必须进行手动地添加。
应用推荐