Relevant for: GUI tests and components and API testing
This dialog box enables you to view or modify the settings that UFT uses when ALM runs a test or business process test on your computer.
Note: For details on accessing UFT and UFT tools and files in Windows 8.X or higher and Windows Server 2012, see Accessing UFT in Windows 8.X or Higher Operating Systems.
User interface elements are described below:
|Restart testing tool after __ runs||
For tests, restarts UFT after ALM completes the specified number of tests runs. When UFT restarts, it continues with the next test in the test set.
For business process tests, restarts UFT after ALM completes the specified number of component iterations. However, if it reaches the specified number of iterations in the middle of a business process test run, it waits until the current business process test iteration is finished before restarting.
You may want to use this option to maximize available memory.
If you do not want UFT to restart during a test set run, enter 0 (default).
|Close testing tool after __ idle minutes when running a scheduled test run||
Closes UFT after it has been idle for the specified number of minutes.
This option is applicable when running tests from Server Side Execution in ALM only. For details on Server Side Execution, see Running tests in Server-Side Execution.
This option is ignored if the test is launched from a non-scheduled ALM test run.
|Run GUITest Sets in debug mode
GUI tests only
Instructs UFT to pause test runs at breakpoints inside in a test.
Note: If you select this option when the Run UFT in hidden mode option is also selected, UFT does not stop at the breakpoints.
|Save the open, modified test before the test run||
If an existing test or keyword GUI component is open in UFT when the Remote Agent begins running a test, this option instructs UFT to save any unsaved changes to the open test or keyword component.
Note: (for GUI testing): This option is not relevant for function libraries. Therefore, if an existing function library is open in UFT when the Remote Agent begins running a test, the function library is not saved.
|Save the open, new test before the test run||
If a new test is open in UFT when the Remote Agent begins running a test, the test is saved in:<Unified Functional Testing>\Tests\ALM with a sequential test name.
Note: (for GUI testing): This option is relevant only for tests. Therefore, if a new keyword component or function library is open in UFT when the Remote Agent begins running a test, the component or function library is not saved.
|Run UFT in hidden mode||
Specifies whether to run UFT in hidden (silent) mode when you run a test set from the Test Lab module in ALM. By default, this option is selected.
Display hidden-mode notification tooltip: If this check box is selected, the Remote Agent displays a tooltip window when UFT runs an ALM test in hidden mode. You can click the tooltip to display UFT during the test set run. By default, this option is selected.
|Keep UFT open after a Test Lab run session ends||
By default, when ALM opens UFT on a remote computer during a test set run (or when it runs selected tests or configurations from the Test Lab module), it closes UFT at the end of that Test Lab run session. This ensures that the UFT license is released at that point and made available for other UFT users.
Selecting this option causes UFT to stay open on your computer (and to continue using the UFT license) after a Test Lab run session ends.
Note: The behavior described above is relevant only when UFT is opened from an ALM server that has the SUPPORT_TESTSET_END parameter set to Y. (Y is the default setting).
If UFT is opened from an earlier version of ALM (or the above-mentioned parameter is set to N), this option is ignored and UFT always remains open at the end of run session.
For details on the SUPPORT_TESTEND_END parameter, see the section on setting ALM configuration parameters in the Application Lifecycle Management Administrator Guide.
|Restart testing tool after||
Restarts UFT if there is no response after the specified number of seconds for:
The default value for both options is 2700 seconds (45 minutes). However, while UFT operations may take a long time between responses, queries usually take only several seconds. Therefore, you may want to set different values for each of these options.
Note: If a function library with unsaved changes is open in UFT, UFT prompts you to save it. If the function library is not saved within 10 seconds, UFT restarts and any unsaved changes are lost.