AutomatedQA的網站上有作了一番解釋
文中提到的TestComplete應該是他們的test tool吧
假裝沒看到它就好
Data-driven testing means that scripts read data from an external storage site, for example, from a file or database, rather than use values hard-coded in the script. Such a separation makes tests logically simpler. A script containing several sets of hard-coded values can be rather difficult to modify. For instance, if you need more input data, you will have to modify the script code.
Normally, the storages hold both input and verifying data. A data-driven test includes the following operations performed in a loop:
- Retrieving input data from storage.
- Entering data in an application form.
- Verifying the results.
- Continuing with the next set of input data
完整文章在此:
http://www.automatedqa.com/products/testcomplete/tc_data_driven_testing.asp
至於Wiki上是這麼說的:
Data-driven testing is a methodology used in Test automation where test scripts are executed and verified based on the data values stored in one or more central data sources or databases. These databases can range from datapools, ODBC sources, csv files, Excel files, DAO objects, ADO objects, etc. Data-driven testing is the establishment of several interacting test scripts together with their related data results in a framework used for the methodology. In this framework, variables are used for both input values and output verification values: navigation through the program, reading of the data sources, and logging of test status and information are all coded in the test script. Thus, the logic executed in the script is also dependent on the data values.
This is similar to Keyword-driven testing in that the test case is contained in the data values and not in the test script; the script is just a "driver" or delivery mechanism for the data. Unlike in keyword-driven testing, though, the navigation data isn't contained in the test script. In data-driven testing, only test data is contained in the data source.
0 意見:
張貼留言