然而，这样做的局限性是不能联合来自不同资产注册表的配置测试用例形成一个套件，从而阻碍了我们的执行。
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.
选择您喜欢的测试选项或者键入您测试套件的名称到适当的字段来开始运行测试用例。
Select the test option that you prefer or enter the name of your test suite in the field provided to start running test cases.
测试套件由测试用例构成，并基于以下两种可用的测试模式之一：操作级别的测试或基于场景的测试。
The test suite is made up of test cases, based on one of two available test patterns: operation-level testing or scenario based testing.
特别需要注意的是，仅仅为测试用例或测试套件添加[parallelizable]属性，并不意味着它一定会和其他的测试并行运行。
Also note that just because a test or fixture is marked parallelizable does not mean it will run in parallel with other tests in particular.
在这个例子中，我们创建了一个叫做MonkeyContactsSuite的套件，它其中包含了一个叫做MonkeyContactsCase的测试用例。
In this example, we've created a suite called MonkeyContactsSuite containing a single test case called MonkeyContactsCase.
阅读Python文档，以深入了解可用于测试套件、测试用例和测试结果的全部范围的方法。
Take a look at the Python documentation for more details on the full range of methods available to test suites, test cases, and test results.
我们会对每个存储层重复执行该测试套件，并且会重新运行这些测试用例2次：一次是测试事务日志恢复，然后测试常规的关闭。
We repeat the test suite for each of our storage layers. Again we rerun those test cases 2 times: once to test Transaction Log recovery and then to test Regular Shutdown.
日志文件的缺陷在于，在测试套件的结尾您无法去决定什么例外与什么测试用例相对应。
The limitation with the log file is that at the end of test suite you are not able to determine which exception belongs to which test case.
严格的SOA应用程序测试意味着在一段时间内建立多个测试用例，并且划分成连续运行的在逻辑上相关的测试套件。
Serious testing of SOA applications means building many test cases over time and dividing them into sets of logically-related test suites that are run continuously.
至此，我们创建了控制器的Selenium测试用例，但在运行之前，我们要先修复Springroo所创建的Selenium测试套件中的一个小缺陷。
Above, we created Selenium test cases for our controller, but before we run them, we need to fix a small defect in the Selenium test suite created by Spring Roo.
通过这种方式使用FlexMonkey，我们可以交互性地创建和维护多种多样的，复杂的，可以包含任意数量测试用例和测试的套件。
Using FlexMonkey in this way we can interactively create and maintain various, complex test suites consisting of any number of test cases and tests.
因为需要运行GoogleTest测试用例，所以，作为参数传递给run方法的测试套件采用GoogleTest . class作为参数。
Because you need to run the GoogleTest test case, the test suite you pass as parameter to run method takes GoogleTest.class as an argument.
只要给测试用例(test)加上[parallelizable]属性，这个测试用例就可以和同一个测试套件(fixture)中其他拥有该属性的测试用例并行运行。
Mark any test [parallelizable] and it will be permitted to run in parallel with other parallelizable tests in the same fixture.
但是，如果使用参数化测试，就可以只定义一个测试用例，然后，(举例来说)把所需的参数模式加到TestNG的测试套件文件中。
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.
最新的内容“利用RedBar状态重构你的测试用例”解决了一个常见的问题。即一旦单元测试套件变得庞大，如何在不破坏测试的前提下进行测试代码的重构呢？
The latest installment (" Refactoring tests in the Red ") tackles a common problem - once a unit test suite becomes substantial, how can the unit tests.
在传统规范中，你首先要手动运行测试用例，然后在程序通过测试后把它添加到自动化套件中。
In the traditional paradigm, you run the test case manually first, then add it to the automation suite after the program passes the test.
通过创建此测试套件，在为团队项目创建的测试用例中，任何使用优先级别字段值1创建的测试用例都将自动添加到此测试套件中。
By creating this test suite, any test case that you create with a value of 1 in the priority field for your team project will automatically be added to this test suite.
若要创建现有测试用例的副本，并将该副本添加到现有测试用例所在的测试套件中，请在测试套件层次结构中选择该测试套件。
To create a copy of an existing test case and add it to that same test suite, select the test suite in the test suite hierarchy.
然后在测试套件细节窗格中显示的测试用例列表中选择现有测试用例。
Then select the existing test case in the list of test cases shown in the test suite details pane.
将测试用例组织成组后，当您要运行所有这些测试时，您就可以更改测试套件的状态。
By grouping your test cases together, when you want to run all these tests, you can change the state of your test suite.
然后，由该查询返回的所有测试用例都将添加到套件中。
Then, all test cases that are returned by that query will be added to the suite.
向计划添加测试套件和测试用例：可以创建测试套件，以便将测试用例进行分组。
Adding test suites and test cases to your Plan: you can create test suites to group your test cases together.
为测试套件创建手动测试用例：在测试计划中的测试套件中，可以创建包含手动测试步骤和期望结果的测试用例。
Creating manual test cases for test suites: you can create test cases with manual test steps and expected results in your test suites in your test plan.
所创建的任何测试用例都与团队项目关联，可以添加到多个测试套件中。
Any test case that you create is associated with your team project and can be added to multiple test suites.
这可使查找测试用例更加轻松，还可以运行测试套件中的所有测试。
Or you can use actions that you record when you run a test to create a test case.
使用测试套件组织测试用例。
使用测试套件组织测试用例。
应用推荐