Relevant for: API testing only
Sometimes, when you are running your test, your data is stored in multiple sources and called by many different step properties in the test. In these cases, you can instruct UFT how to use the data sources, including where in the data source to begin calling data values, how to move through the data source, and where to stop using values from the data source. You specify these settings for each of the data sources associated with your test in the Data Navigation Dialog Box
This is useful to test your application's performance with constantly varying sets of data. In addition, this enables you to maintain your data source while still using it in a test. For example, if you are adding new data to a data source that is being used in a test, but the new data is not complete, you can instruct UFT to begin at the row containing the old data and stop before calling the new data values currently under construction.
The Data Navigation settings you create work with the loop settings for the Test Flow or selected test loop:
If the loop is configured as a ForEach type, and you assign a specific data source as the loop's collection, then the Data Navigation settings affect the number of iterations of the loop. Because you specify the number of rows to use from the selected data source, the test runs the same number of iterations as the number of rows specified.
For data sources that are not designated as the loop collection but whose values are called by steps within the loop, the Data Navigation policy affects the data differently. It indicates the order in which the values are called from the data source and assigned to steps within the loop. For example, if you specify in the Data Navigation dialog box to begin in the second row of your Excel data source, UFT populates the property value with the values from the second row (and so forth, as specified in the Data Navigation dialog box).
For task details, see Set the data source navigation properties.