Improving performance

Relevant for: All tests and components

This topic reviews tips and tricks for improving performance when working with UFT.

Improve GUI testing performance

Use any of the following methods to improve performance when working with GUI tests:

Change area Tips
Starting UFT

Load only the add-ins you need for a specific UFT session when UFT starts.

This speeds up both learning objects and run sessions.

Run session options

Run your tests or components in "fast mode."

From the Test Runs pane in the Options dialog box (Tools > Options > GUI Testing tab > Test Runs node), select the Fast option.

This instructs UFT to run your test or component without displaying the execution arrow for each step, enabling the test or component to run faster.

Screen captures and movie segments

General snapshots.

Reduce disk space and improve test run time by saving screen captures and movie segments only in certain situations, such as when errors occur, or by not saving them at all.

Use the Save still image captures to results and Save movie to results options in the Screen Capture pane in the Options dialog box

(Tools > Options > GUI Testing tab > Screen Capture node)

Insight and snapshots.

If you are using Insight test objects, adjust the number and size of snapshots saved with the test objects.

In the object repository, delete all of the snapshots stored with the Insight test objects after you finalize the test object images and verify that they enable correct object identification in all relevant scenarios.

(In the Object Repository window or the Object Repository Manager, Tools > Delete Insight Snapshots.)

Run results

Save results to a temporary folder

Save the run results report to a temporary folder to overwrite the results from the previous run session every time you run a test or component.

Remove obsolete results

Remove unwanted or obsolete run results from your system, according to specific criteria that you define. This enables you to free up valuable disk space.

BPT

Try to use the same application area for all components in a business process test.

Test actions

Minimize the number of actions in a test. Ideally do not use more than a few dozen actions in each test.

Additionally, store any functions in function libraries instead of as reusable actions.

Active screen

Hide the Active Screen

If you are not using the Active Screen while editing your test, hide the Active Screen while editing your test to improve editing response time.

Right-click the Active Screen pane and select Hide.

Decide if and how much information you want to capture and save in the Active Screen.

The more information you capture, the easier it is to add steps to your test or component using the many Active Screen options.

However, more captured information also leads to slower recording and editing times.

Set your options in the Active Screen pane of the Options dialog box (Tools > Options > GUI Testing tab > Active Screen node).

Determine whether to save Active Screen files

When you save a new test or component, or when you save a test or component with a new name using Save As, choose not to save the captured Active Screen files with the test or component.

Do this by clearing the Save Active Screen files option in the Save or Save As dialog box.

Timeout settings

Decrease the timeout settings for your application.

These settings depend on the application, objects in the application being tested, and the operation being run on the object.

Find these settings in the following locations:

  • In the Run pane of the Settings dialog box (File > Settings > Run), decrease the Object Synchronization timeout.
  • In the Web pane of the Settings dialog box (File > Settings > Web), decrease the Browser Navigation timeout.
Smart identification In the Run pane of the Settings dialog box (File > Settings > Run), disable Smart Identification by selecting the Disable Smart Identification during the run session option.
Saving tests

Save tests on the file system instead of network drives.

Back to top

Recommended test length

There is no formal limit regarding test length.

We recommend that you divide your tests into actions and use reusable actions whenever possible.

Each action should contain no more than a few hundreds steps and, ideally, no more than a few dozen.

For details, see Actions in GUI Testing.

Back to top

Improve performance when working with ALM

Improve performance when working with ALM and UFT or BPT using the following ALM project customization options and site parameters.

Tip: You may need to upgrade to a recent version of ALM to use these options. For more details, see the ALM Help Center.

Upload UFT test results as single zip files

Upload test results as single zip files, making your test results more manageable in ALM.

GUI / API tests

Set the following ALM site parameters to Y:

  • COMPRESS_GUI_TEST_RESULTS
  • COMPRESS_API_TEST_RESULTS
Business Process Testing

Do one of the following:

Project customization

In the ALM Project Customization > Business Process Test > Test Reports area, select the Upload BPT test results to ALM as a single zip file option.

Site parameter

Set the COMPRESS_BPT_TEST_RESULTS ALM site parameter to Y

Handle step parameter values

Exclude step parameter values from the results uploaded to ALM. Do one of the following:

Project customization

In the ALM Project Customization > Business Process Test > Test Reports area, select the Exclude component parameter values from the BPT Report Viewer option.

Site parameter

Set the ENABLE_BPT_STEP_PARAM ALM site parameter to N.

Handle Reporter.reportEvent events

Define the level of Reporter.ReportEvent steps included in the BPT Report Viewer.

Do one of the following to select the lowest report level you want to include:

Project customization

In the ALM Project Customization > Business Process Test > Test Reports area, select a report level.

Site parameter

Set the ALMReportLevel ALM site parameter with the lowest report level you want to include: 

Fail, Warning, Pass, Done

Example: Set this value to Warning to include both Fail and Warning events in your reports.

Back to top

See also: