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 !. "etrieving input data from storage. #. $ntering data in an application form. %. &erifying the results. '. (ontinuing with the next set of input data. )est(omplete includes a number of features to perform these steps. *ou can select the functionality that best suits your needs. Operations

Following are the operations of +ata-driven )esting Retrieving input data from storage ,t is convenient to keep data for tests in special storages that support se-uential access to a set of data, for example, script arrays, text files, database tables, $xcelsheets, and so on. *ou can access data in these storages using scripting ob.ects provided by )est(omplete. )o make the access even easier, )est(omplete includes special features for extracting data from (S& /comma-separated values0 files, database tables and $xcel sheets.

Entering data in an application form )o enter data into application forms and controls, you can either simulate keystrokes, or store data to a property of the desired form or control. )he way you simulate the input depends on many factors. For example, it depends on whether your applicationis compiled as an 1pen Application.

Verifying results )he easiest way to check whether your test actions were performed successfully is to store the check value along with the set of input data and then compare the output with these values. ,f the output is an image or a file, you can use )est(omplete2s features to compare the images or the files3 and ob.ect properties.