被配置的测试用例是由测试用例产生的。
被配置的测试用例具有以下三种可能的状态。
已配置测试用例：带有已应用配置的测试用例。
Configured test case: a test case with a configuration applied.
图6：运行与脚本相关联的已配置的测试用例。
Figure 6: Running the configured test case associated with a script.
这样的话，被配置的测试用例将会继承定义在父测试用例中的脚本。
That way, the configured test case will inherit the script identified in the parent test case.
每个解决方案中的不同配置的测试用例可能测试这个产品相同的区域或者组件。
Different configured test cases in each solution may test the same area or component of the product.
测试计划、测试用例、以及被配置的测试用例都能够被一个或者多个迭代进行标记。
Test plans, test cases, and configured test cases can all be tagged with one or more iterations.
被配置的测试用例是在您将一个特定的配置关联到一个特定的测试用例时被创建的。
Configured test cases are created when you relate a specific configuration to a specific test case.
在测试计划中，团队的最后一个步骤涉及到通过迭代“标注”他们的被配置的测试用例。
The team's final step in test planning involves "tagging" their configured test cases with the iteration for which they intend to run them.
测试计划、测试用例，以及被配置的测试用例(CTC)记录都拥有一个owner域。
Test plan, test case, and configured test case (CTC) records all have an Owner field.
在完成这个操作之后，他们就能够创建查询和报告，显示他们所计划的被配置的测试用例。
After this is done, they can create queries and reports to show the configured test cases that they have planned.
根据图7中的屏幕捕获，您能够看到，当前所有被配置的测试用例都被指派为admin。
Based on the screen capture in figure 7, you can see that, currently, all configured test cases are assigned to Admin.
由于被配置的测试用例才是您将要实际运行的，所以一个好的实践就是适当的在CTC上设置所有权。
Because configured test cases are what you will actually run, it is a good practice to set ownership on CTCs appropriately.
正如前面所描述的，ClearQuest测试管理允许您将多个迭代同一个被配置的测试用例关联起来。
As described earlier, ClearQuest test management allows you to associate multiple iterations with a single configured test case.
这样的话，您只需要打开一个被配置的测试用例，并且查看相关联的日志文件，就可以看到所有发布的执行结果。
This way, you simply need to open a configured test case and view the associated logs to see the execution results history across all releases.
通过图4所示的对话框，用户可以选择deviceanywhere脚本来与由ClearQuest配置的测试用例相关联。
Through the dialog box shown in figure 4, users select a DeviceAnywhere script to associate with a ClearQuest-configured test case.
图4：通过图4所示的对话框，用户可以选择deviceanywhere脚本来与由ClearQuest配置的测试用例相关联。
Figure 4: Through the dialog box shown in figure 4, users select a DeviceAnywhere script to associate with a ClearQuest-configured test case.
通过ClearQuest测试管理中的一个迭代来跟踪测试进度需要您创建一个迭代，然后选择若干被配置的测试用例来同这一迭代相关联。
Tracking testing progress with an iteration in ClearQuest test management requires you to create an iteration, and then to select some number of configured test cases to associate with the iteration.
如果您需要为属于同一个父测试用例的每一个被配置的测试用例建立不同的脚本的话，那么这些脚本将在您创建被配置的测试用例之后被关联起来。
If you require different scripts for each configured test case belonging to the same parent, then the scripts can be associated after you create the configured test cases.
当您将一个新的测试日志提交到数据库的时候，ClearQuest就会通过运行一个搜索来决定是否存在一个用于同一个被配置的测试用例和同一个迭代的日志文件。
When you commit a new test log to the database, ClearQuest runs a search to determine whether there is an existing log for that same configured test case, for that same iteration.
这些信息让用户可以从ClearQuest界面启动DeviceAnywhere，并且将由ClearQuest配置的测试用例与deviceanywhere脚本关联起来。
This information allows the user to both launch DeviceAnywhere from the ClearQuest interface and associate ClearQuest-configured test cases with DeviceAnywhere scripts.
键入您的配置测试用例的名称。
您可以使用默认的测试用例报告来根据计划、配置，或团队列出测试用例。
You can use the default test case reports to list test cases by plan, configuration, or team.
当您执行这些操作时，树形视图将会立即被加载上测试用例特定的被配置的版本。
When you do this, the tree view is immediately populated with specific configured versions of the test cases.
然而，这样做的局限性是不能联合来自不同资产注册表的配置测试用例形成一个套件，从而阻碍了我们的执行。
However, the limitation of not being able to associate configured test cases from different asset registries to form a suite prevented us from implementing this.
它包括阅读测试工具创建的测试日志的能力，以及为已配置测试用例创建测试日志结果的能力。
It includes the ability to read test logs created from the testing tool and to create test log results for the configured test case.
在测试用例被设置之后，团队就能够开始通过配置来标记他们的测试用例，并且创建被配置过的测试用例(CTC)。
After the test cases are set up, the team can begin to tag their test cases with configurations to create configured test cases (CTCs).
如图6所示，测试集的状态与已配置测试用例的状态是一样的，因为一套就代表一组已配置测试用例。
As figure 6 shows, the states for a test suite are the same as for a configured test case, because a suite represents a group of configured test cases.
默认情况下，这个状态查询不包括显示配置测试用例缺陷数量的字段。
By default, the state queries do not include a field to display the defect number for configured test cases.
配置：定义一个测试用例的环境，比如操作系统，机器规格，软件版本等等。
Configuration: Defines the context of a test case, such as operating system, machine specification, software version, and so on.
应用推荐