In practice a test fixture usually is a combination of setup and teardown functions, associated with test case.
实际上测试夹具通常是安装和拆卸函数的组合,和测试用例结合。
In this case the tree looks different: you start with test cases, and then trace back from scenarios and use cases.
在此种情况下,追踪树看起来会有不同:你从测试用例开始,然后追踪场景和用例。
If, for instance, the test case with 100*40000 files fails, then how do you go about it?
例如,如果采用 100*40000 个文件的测试用例失败,那么如何进行相关工作呢?
A best practice in most software development lifecycle practices is the tracking requirements associated with your test case.
大多数的软件开发生命周期的最佳实践,是追踪与测试用例相关的需求。
After I made these code changes, I used the debugger to verify that the object count associated with the deleted form decreased when the same test case was executed.
当作了这些修改以后,我使用调试器证实:当执行相同的测试案例时,与被删除的窗体相关联的对象计数减小。
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.
性能测试实现的一个重要特点是,使用常规的功能性和集成测试用例,但是采用大型测试数据集和沉重的负载。
In that case (so we agree with all stakeholders), we build the code, and test and document it following the SAD.
在那种情况下(我们与所有的涉众达成一致),我们构建代码,并且根据SAD测试和编制文档。
Moreover, these inputs, because of their specialized nature, are clear, with direct information easily converted into a test case for the appropriate test phase.
此外,由于他们特殊的本质,这些输入十分清晰,而且这些信息很容易就可以转化成适当的测试阶段的测试用例。
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。
The notion that you can generate a viable architecture by starting with a blank screen and then writing one test case after the other is sheer folderol.
以为通过在白板上编写一个个测试用例就可以产生清晰架构的想法简直就是胡闹。
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配置的测试用例相关联。
But with parametric tests, you can define one test case and then push your desired parameter patterns (for example) into TestNG's suite files. That's what I've done in Listing 6.
但是,如果使用参数化测试,就可以只定义一个测试用例,然后,(举例来说)把所需的参数模式加到TestNG的测试套件文件中。
Now the functional test script, S1, is associated with the TestManager test case, TC1.
现在功能性测试脚本,S1,就与TestManager测试用例,TC1联系在一起。
Once a script is ready, users can execute it by running the configured test case associated with ClearQuest.
一旦脚本准备好,用户就可以运行与ClearQuest相关的配置好的测试用例来执行脚本。
By default, EasyMock only allows the test case to call the methods you specify with the arguments you specify.
在默认情况下,EasyMock只允许测试用例用指定的参数调用指定的方法。
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看起来似乎是一个附加的测试类型。
With this matrix, you can generate a similar test case and requirement association report using the Rational ClearQuest environment.
有了这个矩阵,您就可以使用RationalClearQuest环境生成一个相似的测试用例与联系报告了。
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”链接。
This test case will fail at assertion because the results page contains no link with this text.
这个测试用例遇到断言的地方会失败,因为结果页面中不包含带有这个文本的链接。
If you have a bumper case and can test with the bumper case on, that would be great.
如果有新发现请和我们联系。如果你有原厂的胶套的话可以试试套上胶套进行测试。
As with manual test scripts, to run an automated script, you must associate it with a test case and a test execution (test run) record.
至于手动设置的测试脚本,为了运行一个自动化的脚本,您必须将其与一个测试用例和测试执行(测试运行)记录联系起来。
应用推荐