The data-driver populates a datapool with data from the application. A datapool is a collection of related data records. A datapool supplies data values to the variables in a test script during test script playback.
You can use two methods to select an object:
To data drive a test script:
The Functional Tester window minimizes and the Recording Monitor opens.
See Starting Your Test Applications for more information. (If your application is already running, you do not need to do this step.)
The test script recording pauses and the Insert Data Driven Actions page opens.
By populating these fields while the recorder pauses, you do not record unnecessary actions in the test script. Any change to the control flow of the program while the test script recording pauses is not recorded in the test script.
Functional Tester outlines the object with a red border.
The Data Drive Actions page opens. In the Data Drive Actions page, under the DataDriven Commands table, information appears about the objects you selected.
You can place your mouse pointer over a row in this table to view the line of code that Functional Tester inserts into the test script to data-drive the application-under-test.
Functional Tester outlines the object with a red border.
The Insert Data Driven Actions page opens with information filled in under Data Driven Commands and Selected Command Description.
For example, you can change the initial value of a test object to test the non-default states of an application.
You can use a datapool reference instead of a literal value for the value you are testing in the verification point.
Click the Help button in the Script Support Functions dialog box for information on these functions.
The Functional Tester window opens and the script displays in the editor window.