Configure run result export details

Relevant for: GUI testing and API testing

What is the Configuration Automatic Export dialog box? This dialog box enables you to define settings that instruct OpenText Functional Testing to automatically export run results to a specific folder in the file system after a run session. The exported file can then be sent to another user to open in the Run Results Viewer.

Option Description

To access

  1. Select Tools > Options > General tab > Run Sessions node to open the Run Sessions pane.

  2. Under Report Format, select Run Results Viewer Report.

  3. Select Automatically export run results when run session ends.

  4. Click the Configure button.
Important information

  • This option is not supported for business components and business process tests.

  • When running API tests from the Test Batch Runner, the run results cannot be automatically exported as a PDF. Instead, open the results in the Run Results Viewer and export them manually, as described in Export run results.

See also Run Results Viewer Report

What details can you set for exporting?

UI Element

Description
Step Details

The main report type. This includes the entire run results tree. (Default)

  • Export type. The file type for the exported results. Possible options:

    • HTML (Default)

    • PDF

    • Doc (Displayed when you have Microsoft Office installed on your computer)

  • Export format. The format and amount of detail to include in the exported results. Possible options:

    • Short. Exports a summary line (when available) for each item in the run results tree. The short report does not include still images associated with the steps in your run results. (Default)

    • Detailed. Exports all available information for each item in the run results tree. The detailed report includes still images associated with the steps in your run results. (In the Run Results Viewer, these images are displayed in the Captured Data pane.) If a bitmap checkpoint step displays expected, actual, and difference bitmaps, these are also included in the printed report.

    • User-defined XSL. Enables you to browse to and select a customized .xsl file. You can create a customized .xsl file that specifies the information to be included in the exported report, and the way it should appear.
Screen Recorder
(GUI testing only)

A video of the run session.

Note: Screen capture images are not exported for steps on Web-based applications. When you export run results containing steps on a Web application, any screen capture images for those steps are not exported to the file. This is because for Web-based applications, the run results display the HTML corresponding to the relevant Web page (with downloaded images) rather than a captured image and thus no image is saved with the report.
Data Table

The runtime version of the data table associated with your ALM configuration. It displays the values used to run a test or configuration that contains Data Table parameters, as well as any output values retrieved from a test or an ALM configuration during a run session.

Log Tracking
(GUI testing only)

A complete list of log messages that OpenText Functional Testing received from your application during the run session.

System Monitor
(GUI testing only)

The system counters that are monitored for a run session displayed in a line graph.
Export location

The folder in which to store the exported files. Clicking the browse button opens the Browse For Folder dialog box, enabling you to select a folder on the file system.

If you do not specify a folder, the files are automatically exported to the default folder: <test folder>\<result folder>\Report. (For example, %HOMEPATH%\Documents\Functional Testing\Res9\Report.)

Export run results only if the run session fails

  • Select this checkbox to export run results only for failed run sessions.

  • Clear this checkbox to export all run session results.

Where are these options saved?

The export options are store in the ReportExportOption.xml file. This file is useful when using the Test Batch Runner from the command line.

The file is located in the %AppData%\OpenText\UFT\ConfigurationUI folder.

Note: Some folder paths intentionally include previous company branding, due to backward compatibility considerations.