Run Dialog Box

Relevant for: GUI testing, API testing, and business process testing

This dialog box lets you prepare for the test run by selecting the test to run and providing a location for the results.

To access

  1. Ensure that a test or component is in focus in the document pane or selected in the Solution Explorer.

  2. Select one of the following:

    • Click the Run button.

    • For GUI tests:

      • Click the Run button and select Maintenance Run Mode.

      • Click the Run button and select Update Run Mode.
Important information

  • When the test stops running, the run results open unless you have cleared the View results when test run ends check box in the Run Sessions pane of the Options dialog box (Tools > Options > General tab > Run Sessions node).

  • You can also optionally automatically upload your run results to ALM if you are running a test from ALM. This option is set in ALM as a site parameter for your project. For details, see the Application Lifecycle Management Administrator Guide.

  • When running API tests, you can bypass this dialog box using the Run > Run Now menu item.

  • For GUI testing: When running a test with external resource files (like function libraries, data tables, or recovery scenarios) that are saved in ALM, the resource files are not refreshed for each test run. As a result, any changes made to these external resource files during the current session are not reflected in a test run until you close and reload test and its resource files.
Important Information (for business process tests and flows)

When you run business process tests and flows in UFT One, you can only select the document you are running, if you have multiple documents open. You cannot modify the results location, nor can you define any other options.

Note: For improved performance when running business process tests or flows, UFT One creates and runs a hosting test, named Test Runtime. The Test Runtime test is recreated each time the test or flow runs, and is not saved with the run.

Relevant tasks

User interface elements are described below:

UI Elements

Description
Test Name

The test or component to run. You can select any open item from the drop-down list.
Results Location
(for GUI, API, and business process tests)

The target location for the results.

For GUI and API tests, you can specify this location in the Results Location tab.

For business process tests, results are always saved in the temporary run results folder.
Options
(for GUI and API tests)

Expands or collapses the dialog box to show the Results Location and Input Parameters tabs.
Run

Begins the run session.

This tab enables you to specify where to save run results when running tests stored on the file system.

User interface elements are described below:

UI Elements

Description
New run results folder

An area allowing you to indicate the results location.

The area displays the default path and folder name in which the results are saved. A new folder is created for each run. By default, results are stored in the following locations:

  • For tests: The test folder

  • For components: An ALM cache folder on your computer
Temporary run results folder

Saves the run results in a temporary folder. This option overwrites any results previously saved in this folder.

Note:  

  • The path in the text box of the Temporary run results folder option cannot be changed. Additionally, if you save results to an existing results folder, the contents of the folder are deleted when the run session starts.

  • UFT One stores temporary results in %TMP%\TempResults (which is usually <System Drive>\Documents and Settings\<user name>\Local Settings\Temp\TempResults).

This tab enables you to specify where to save run results when running tests stored in ALM.

User interface elements are described below:

UI Elements

Description
New run results in ALM project

  • Project name. Displays the ALM project to which you are currently connected.

  • Run name. The name of the run. You can accept the automatically generated name or enter a different one.

  • Test set. A group of tests selected to achieve specific testing goals. For example, you can create a test set that tests the user interface of the application or the application's performance under stress. (You define test sets when working in the ALM test run mode. For details, see your ALM documentation.)

  • Instance. The instance of the test in the test set. If there is more than one instance, select the instance of the test for which you want to save the results.
Temporary run results folder

Saves the run results in a temporary folder. This option overwrites any results previously saved in this folder.

  • The path in the text box of the Temporary run results folder option cannot be changed. Additionally, if you save results to an existing results folder, the contents of the folder are deleted when the run session starts.

  • UFT One stores temporary results in %TMP%\TempResults (which is usually <System Drive>\Documents and Settings\<user name>\Local Settings\Temp\TempResults)

This tab enables you to specify to specify the run-time values of input parameters to be used during the run session.

User interface elements are described below:

UI Elements

Description
Input parameters

The input parameters that were defined for the test or component.

To set the value of a parameter to be used during the run session:

Click in the Value field for the specific parameter and enter the value, or select a value from the list. If you do not enter a value, it uses the default value from the Test Settings or Business Component Settings dialog box during the run session.