Using Run Results
Relevant for: GUI tests and components,API testing, and business process tests and flows
After you run a test or component, UFT displays results that detail the success or failure of each step, and the reasons behind each failure (if necessary). These run results are opened automatically as a separate tab in the document pane immediately after the test or component run.
The run results are saved on a single HTML page, with links to other resources, such as the data table used with a test run, screen captures of the application being tested, and movies of the test run. Because the run results are saved in HTML format, they can be exported and/or sent to other people without the need to have UFT installed.
To view the run results on your browser, you should use one of the following browsers:
Internet Explorer 10 or higher (with Compatibility Mode disabled)
The latest supported version of Chrome.
Working with ALM:
If you save UFT run results in an ALM version earlier than 12.50, results are displayed in the Run Results Viewer format even if the HTML report is set in the Run Sessions pane of the Options dialog (Tools > Options > General tab > Run Sessions node).
If you are running a business component, the HTML report option is supported only from ALM versions 12.53 and higher.
You can also view run results in the Run Results Viewer. For details, see the
In the run results, you can see a description of each step in your test (even if the test or a specific action ran over multiple iterations), with details about application objects and test objects used in the step, and the properties used to identify the test object:
You can also choose to filter what items are shown in the test flow.
In addition to viewing only the test flow, you can view specific information about the errors (including warnings) that occur in your test flow. The run results give a description of the error, including the test object used and the expected result. For checkpoints, the checkpoint details (as selected in the Checkpoint Properties dialog box for a GUI test) are also displayed:
As part of the test step result details, you can see a screen capture of your application during the run session, either for every step or for steps with errors. For steps or errors on specific object in the application, UFT highlights the application object in the screen capture:
You select the level of screen capture detail in the Screen Capture pane of the Options dialog box (Tools > Options > GUI Testing tab > Screen Capture node).
When you encounter an error in your test, you may need to perform some investigation to find where the error occurs. To help with this, the run results display a call stack log for any errors encountered during the test run:
In the Screen Capture pane of the Options dialog box (Tools > Options > GUI Testing tab > Screen Capture node), you can instruct UFT to capture a movie of the run session. The run results provide a link and enable you open the file directly from the results:
If you send the run results which have a movie to another user, you must send the entire folder containing the run results. If you do not, the movie link will not display the movie.
With the run results, you can open the data table used with the test run directly from the run results. The run results provide a link and you simply open the file on your computer:
If you send the run results which have a data table to another user, you must send the entire folder containing the run results. If you do not, the data table link will not display the data table.
When you run steps in a GUI test using the Reporter object, these messages are displayed in the run results, in the step in which they are run. For details on the Reporter object, see the Utility Objects section of the UFT Object Model Reference for GUI Testing.
For each API test step, the run results report the property values used to run each step. These values are reported in a grid which shows the input and output values.
This grid also includes any custom messages send to the run results with event handler code.
For each API test step in the test flow, the run results provide the captured values as part of the test step summary:
When you run a business process test in UFT, UFT can display all the details of the entire structure of your test, including:
Business process flows
Steps with all types of components, including scripted GUI components, keyword GUI components, and API components
The example below shows the results from a business process test:
Within each type of component, the individual steps are displayed in the same way as for a GUI test or API test, with each test step displayed separately and details in the Details pane.