建立一个数据驱动测试套件。
数据选择是沿着数据驱动测试之路的第一步。
Data selection is the first step down the road of data-driven testing.
忘记有更少的代码吧，了解数据驱动测试在测试什么将更容易。
Forget how much less code there is, it's easier to tell what the data-driven test is testing.
考虑一下能在您的自动化测试中使用的一些数据驱动测试的方式。
Think about some of the ways you can use data-driven testing in your test automation.
数据驱动的场景：建立即时的数据驱动测试，提高测试覆盖率。
Data driven Scenarios: This allows to build data-driven tests on the fly for increased test coverage.
不要觉得好像如果您想要进行数据驱动测试，您就需要立刻转换您所有的脚本。
Don't feel like if you want to do data-driven testing that you need to convert all of your scripts at once.
它为功能性的测试、回归测试、GUI测试以及数据驱动测试，提供了自动化的测试功能。
It provides automated testing capabilities for functional testing, regression testing, GUI testing, and data-driven testing.
虽然框架通常与一个或一个以上的数据驱动测试策略一同使用，但它本身却提供了一种完全不同的方法。
The framework provides an entirely different approach, although it is often used in conjunction with one or more data-driven testing strategies.
在这样的情况下，使用JUnit的测试人员往往会转而使用FIT这样的框架，因为这样就可以用表格数据驱动测试。
JUnit testers often turn to a framework like FIT in this case because it lets you drive tests with tabular data.
InfoQ：与其它像DBUnit之类的数据测试框架相比，Twist 2.0的数据驱动测试场景怎么样？
InfoQ: How does the data Driven test Scenario feature in Twist 2.0 compare with other data testing frameworks like DBUnit?
数据驱动测试是一项单个测试脚本使用不同的输入和响应数据被重复地执行的技术，这些数据来源于一个预定义的数据集。
Data-driven testing is a technique where a single test script is used repeatedly with varying input and response data that comes from a predefined data set.
介绍了一种自动测试系统(ats)软件结构，在该结构中，应用数据库管理测试数据，并通过测试数据驱动测试系统工作。
A software architecture of automatic test system (ATS) is introduced. Database is used to manage the data of test, and the system is drived by the data in this software architecture.
RationalPerformance Tester为功能性的测试、回归测试、GUI测试以及数据驱动测试，提供了自动化的测试功能。
Rational Performance Tester provides automated testing capabilities for functional testing, regression testing, GUI testing, and data-driven testing.
当您在RationalFunctionalTester里创建一个数据驱动测试时，您可以用不同的输入和响应数据来重复地使用单个测试脚本。
When you create a data-driven test in Rational Functional Tester, you can use a single test script repeatedly with varying input and response data.
这个工具包中有用于加载数据库和驱动基准测试程序的一些基准工具。
Inside the kit are the benchmark facilities for loading the database and driving the benchmark.
那么，从保存数据对象的XML表示形式的外部配置文件驱动测试似乎比较明智。
It seems wise, then, to drive the tests away from external configuration files holding XML representations of the data objects.
我们已经让编写数据驱动的测试变得更加简单。
一个可以使脚本成为数据驱动并开始向开发人员已经编码的简单用例中添加更多用例的测试人员立即得到了该脚本。
The script is immediately available to a tester, who can make the script data-driven and start adding more cases to the simple cases the developer already coded.
对于这个应用程序，测试用例非常特殊和集中(并且依靠于GUI)，以至于数据驱动框架就没有意义了。
For this application, test cases were so specific and focused (and GUI dependent) that a data-driven framework didn't make sense.
列表3显示了相同的测试脚本，只是脚本现在是数据驱动的。
Listing 3 shows the same test script, only now it's data-driven.
数据驱动框架的主要优势是它减少了为很多类型的应用程序创建测试用例的成本。
The main advantage of a data-driven framework is that it reduces the cost of creating test cases for many types of applications.
数据驱动框架最大的缺点之一是，它创建新的测试用例太容易了。
One of the most prominent drawbacks to a data-driven framework is that it makes creating new test cases so easy.
DB 2：下载DB 2 9.5数据服务器的测试驱动程序。
若要使用实际的数据库驱动的事件来测试整个应用程序，请再次打开DB 2命令中心。
To test the entire application with real database-driven events, open the DB2 command center again.
对比数据驱动的框架(本系列中所涵盖的下一个框架)，在那您更加关注于将数据从您的测试用例中提取出来。
Contrast that to a data-driven framework (the next framework covered in this series) where you are more concerned with abstracting the data from your test cases.
fixture类的作用相当于驱动程序，确定如何根据SUT来测试表中的示例数据集。
The fixture class ACTS as the driver to determine how the sample data sets in the table are to be tested against the SUT.
我们正努力给大家提供一种方式，通过大型数据集驱动测试场景。
We are trying to give people a way to drive their testing scenarios via a large data set. Say for example you've written the following test in Twist
图7：测试套件数据驱动表的实例。
这将显示出系统在测试时的内部情况，因为数据收集机制是在系统测试下进行的，而不是负载驱动的。
This shows the inside of the system under test, because the data collection mechanisms are on the systems under test, not the load drivers.
从测试驱动器客户机指标文件收集响应时间数据。
Collect the response time data from the test driver client metrics file.
应用推荐