Creating a test suite without using macros.
创建不使用宏的测试套件。
A test suite architecture centered around decision points
以决策点为中心的测试套件体系架构
At the system use-case level, a test suite implements the use-case scenarios.
在系统用例层面，一个测试套件实现用例场景。
So as we look at testing, what we have to find is what's called a test suite.
当我们谈到测试的时候，我们必须明白什么叫做一个测试集。
Note that TestRunner is not the only way to run a single test or a test suite.
注意，TestRunner并非运行单一测试或测试套件的惟一方法。
As of Rails 3, Rails will have a defined public API with a test suite for that API.
从Rails3开始，Rails将拥有一个定义好的公共api，同时还带有一个测试套件。
Usually multiple test cases are added to a test suite and the complete suite is run.
通常来说，多个测试用例会添加至一个测试套件中，然后才会运行完整的套件。
Listing 22 has a test suite in which only one out of three tests is using fixture.
在清单22给出的测试套件中，三个测试中只有一个使用装备。
Then you can run these tests from your test plan by selecting a test suite to run.
接著可以透过选取要执行的测试套件，来执行测试计划中的这些测试。
What is really cool, though, is that the unit tests function as a test suite for vendors.
但是，真正“炫酷”的地方在于这些单元测试的作用是作为面向供应商的一个测试套件。
For example, imagine a test suite that tests a Web application that requires a login.
例如，假设有一个测试套件测试一个需要登录的Web应用程序。
Finally, JUnit 4 has no suite methods that build a test suite out of multiple test classes.
最后，JUnit4没有suite方法，这些方法用于从多个测试类构建一个测试套件。
A huge issue in designing and writing a test suite is how to handle common setup and teardown code.
在设计和编写测试套件时，一个大问题是如何处理共同的setup和teardown代码。
You must associate your automated tests with test cases and add them to a test suite in a test plan.
您必须建立自动化测试与测试案例的关联，并将它们加入到测试计划中的测试套件。
Running manual tests in a test suite using test Runner can help you identify problems in software code.
使用测试执行器来执行测试套件中的手动测试，可协助识别软体程序码中的问题。
If the error is encountered during the execution of a test suite, a link to the test suite report is printed.
如果在测试套件执行期间遇到错误，则输出连接到测试套件报告的链接。
Perhaps you're writing a test suite for such a library and find writing the testing code a tedious task.
也许你正在为这些类库编写测试用例，但是发现这是一个让人烦躁的工作。
All the elements of a test suite are defined in a driver table that specifies an un-ordered set of test segments.
一个测试套件的所有元素都在一个驱动表中被定义，在这个驱动表中列出了一系列无序的测试片断。
To create a test suite without macros, instantiate CppUnit::TestSuite, and then add individual tests to the suite.
要想创建不使用宏的测试套件，应该实例化CppUnit::TestSuite，然后在套件中添加测试。
Start with new code, get used to the process, and then revisit the existing code to create a test suite for it.
首先从新代码着手，待您习惯了整个过程以后，再针对现有代码创建测试程序。
Suppose you create a test suite that includes a case that expects the document in Listing 1 as a correct output.
假设要创建一个包含案例的测试集，想以清单1中的文档作为正确的输出结果。
That said, it does not mean that there cannot be a test suite module file that loads all the unit tests for all modules.
但这不意味着不允许任何能够加载所有模块的全部单元测试的测试套件模块文件的存在。
The CPPUNIT_TEST_SUITE macro, defined in HelperMacros.h, simplifies creating a test suite and adding individual tests to it.
在HelperMacros . h中定义的CPPUNIT _ test_suite宏可以简化创建测试套件并在其中添加测试的流程。
Now, let's try to make a test suite using Boost that tests a software product the way an external tool user typically sees it done.
现在，我们使用Boost创建一个测试套件，以外部工具用户常见的方式测试软件产品。
As a valuable side effect, you end up with a test suite that can help prevent the introduction of regressions when you maintain the code.
这样做会同时产生另一个有价值的结果，即您最终会有一个测试套件，它有助于在维护代码时预防回归的引入。
Thus, the tester must design test suites according to the test architecture, and it makes sense to have a test suite that runs test suites.
因此，测试人员必须根据测试选择设计测试套件，并且拥有一个运行测试套件的测试套件是有意义的。
Indeed, the JUnit framework would let us create a test suite dynamically at run time, the suite being derived from the available test data.
事实上，JUnit框架在运行时允许我们动态创建测试套件，该套件源自可用的测试数据。
Such tools include a test suite, MVC architecture, code generators, gem based plugins, environment stages, and easy application configuration.
这些工具包括有一个测试套件、MVC架构、代码生成器、基于gem的插件、环境场景，以及轻便的应用程序配置。
There's no point in spending time and money to run a test suite, even one that passes all its tests, if it doesn't really exercise the project.
如果它不能真正运行这个项目，就没有必要花费时间和资金来运行这个测试套件，即使能够通过它所有的测试。
The existence of working code is a wonderful thing for setting up a test suite that defines what the problem you want to solve is, exactly.
得到已经正常运转的代码是非常有用的，这样可以制定测试组件，来精确定义你到底要解决什么问题。
应用推荐