In Exercise 4a: Run a test, you ran the Book Flights test you created. After the test run is finished, the run results automatically display the results for this test run.
Note: By default, the run results are displayed in an HTML-based report. You can also choose to have the run results displayed in the Run Results Viewer in the Run Sessions pane of the Options dialog box (Tools > Options > General tab > Run Sessions node). The lessons in this tutorial are based on the HTML-based report.
When the run results open, UFT displays the following:
By default, the run results display the following:
|Test Flow||A graphic representation of the results in a tree, organized according to the actions and the application pages visited during the test run. The steps performed during the run are represented by icons in the tree, which can be expanded (arrow) to view each step. You can instruct UFT to run a test or action more than once using different sets of data in each run. Each run is called an iteration, and each iteration is numbered. (The test you ran had only one iteration.)|
|Error list||A list of all the errors and warnings, presented in a list.|
|Step summary information||A high-level results overview report, containing general information about the test, which steps passed or failed, and details about each test step..|
|Links to external resources||
Links to external resources used with your test or from the test run, including:
In this exercise, the test run succeeded because UFT was able to navigate the flight booking application according to the steps you added. If an error occurred and your test did not run successfully, the error will be shown in the run results. In such cases, go back and make sure that the steps are configured exactly as described in this tutorial.