In practice a test fixture usually is a combination of setup and teardown functions, associated with test case.
实际上测试夹具通常是安装和拆卸函数的组合，和测试用例结合。
If, for instance, the test case with 100*40000 files fails, then how do you go about it?
例如，如果采用 100*40000 个文件的测试用例失败，那么如何进行相关工作呢？
First I wrote a test case with an unguarded log statement.
首先用一条未监护的日志语句编写一个测试案例。
A best practice in most software development lifecycle practices is the tracking requirements associated with your test case.
大多数的软件开发生命周期的最佳实践，是追踪与测试用例相关的需求。
After you import the test script, associate it with a test case.
在您导入测试脚本之后，将其与一个测试用例联系起来。
You would want to correlate each test case id with an identified expected result.
您会想将每个测试用例id与一致的期望结果关联起来。
After you have written the test case or configured test case, you can modify it and associate it with the script.
当您编写完这个测试用例或者配置测试用例以后，您就可以对它进行修改并将它与脚本连接起来。
Each configured test case needs to be associated with at least one iteration.
每个已配置测试用例需要至少与一次迭代相关联。
An important aspect of performance testing implementation is the usage of a regular functional and integration test case in connection with large test data sets and extensive loads.
性能测试实现的一个重要特点是，使用常规的功能性和集成测试用例，但是采用大型测试数据集和沉重的负载。
The test case creates two class loaders, each with what appears to be the same classpath.
测试用例创建了两个类装入器，每个类装入器使用的类路径看起来相同。
The test case will be associated with the requirements you've selected.
测试用例就会与您选择的需求联系起来了。
Select the functional test script name, S1, which you need to associate with the TC1 test case, and click OK.
选择功能性测试脚本名，S1，您需要将其与TC1测试用例相联系，并点击OK。
Through the dialog box shown in figure 4, users select a DeviceAnywhere script to associate with a ClearQuest-configured test case.
通过图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.
图4：通过图4所示的对话框，用户可以选择deviceanywhere脚本来与由ClearQuest配置的测试用例相关联。
Associate a script with the configured test case.
将一个脚本与这个配置测试用例连接起来。
Associate your requirement with a test case.
将您的需求与一个测试用例联系起来。
Now the functional test script, S1, is associated with the TestManager test case, TC1.
现在功能性测试脚本，S1，就与TestManager测试用例，TC1联系在一起。
Associate a test script with your test case.
将一个测试脚本与您的测试用例联系起来。
Figure 6: Running the configured test case associated with a script.
图6：运行与脚本相关联的已配置的测试用例。
Once a script is ready, users can execute it by running the configured test case associated with ClearQuest.
一旦脚本准备好，用户就可以运行与ClearQuest相关的配置好的测试用例来执行脚本。
The following steps cover how to develop the EJB, set up the Cactus framework, write your test case, and unit test with the test case that you will create.
下面几个步骤是关于如何开发e JB、安装Cactus框架、编写测试案例以及对将创建的测试案例进行单元测试的。
From there, it is a straightforward call to AmbulantPlayer_gtk with a test case as a single argument as in Listing 2.
在这里，可以使用一个测试用例作为单个参数(如清单2中所示)对AmbulantPlayer_gtk进行直接调用。
I chose the Tesseract output from Listing 2, with its faults, as the test case for input into the script.
我选择了清单2的Tesseract输出及其错误作为此脚本输入的测试用例。
After their adapter is installed, QAInspect appears as an additional test type when you associate an implementation with a test case or configured test case.
当它们的适配器安装以后，您将一个执行与一个测试用例或者已配置测试用例联合起来时，QAInspect看起来似乎是一个附加的测试类型。
As you can see in Listing 7, the test case is executed with HttpUnit Hwee as a parameter.
正如在清单7中可以看到的，可以用HttpUnitHwee作为参数来执行测试用例。
Listing 1 shows an example test case written with HttpUnit that tries to click on the "Cookbook" link on the HttpUnit home page.
清单1显示了一个用HttpUnit编写的测试用例，它试图单击HttpUnit主页上的“Cookbook”链接。
The test case is realized with an activity diagram.
测试用例是通过一个活动图实现的。
The test case itself must also be written with the understanding of an asynchronous context.
必须要在了解异步上下文的基础上对这个测试示例本身进行编写。
If you have a bumper case and can test with the bumper case on, that would be great.
如果有新发现请和我们联系。如果你有原厂的胶套的话可以试试套上胶套进行测试。
Configured test case: a test case with a configuration applied.
已配置测试用例：带有已应用配置的测试用例。
应用推荐