Improving GUI testing performance

Relevant for: GUI tests and components

How can I improve the working speed of UFT when working with GUI testing?

You can improve the working speed of UFT by doing any of the following:

  • Load only the add-ins you need for a specific UFT session when UFT starts. This will improve performance while learning objects and during run sessions.
  • 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.
  • 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).
  • If you are using Insight test objects, adjust the number and size of snapshots saved with the test objects.

    In the object repository, you can 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.)

  • 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.
  • Try to use the same application area for all components in a business process test.
  • Minimize the number of actions in a test. Ideally, a test should not contain more than a few dozen actions.
  • Store your functions in function libraries instead of as reusable actions.
  • 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.
  • 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 by right-clicking the Active Screen pane and selecting 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, but 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).
  • When you save a new test or component, or when you save a test or component with a new name using Save As, you can choose not to save the captured Active Screen files with the test or component by clearing the Save Active Screen files option in the Save or Save As dialog box.
  • 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. You can 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.
  • 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.

  • Save tests on the file system instead of network drives.

Back to top

How can I decrease the disk space used by UFT for GUI tests and components?

  • Save screen captures and movie segments only in certain situations, such as when errors occur, or by not saving them at all. with 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).
  • If you are using Insight test objects, adjust the number and size of snapshots saved with the test objects.

    In the object repository, you can 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.

  • When you save a new test, or when you save a test with a new name using Save As, you can choose not to save the captured Active Screen files with the test by clearing the Save Active Screen files option in the Save or Save As dialog box. This is especially useful when you have finished designing your test and you plan to use your test only for test runs. Tests without Active Screen files use significantly less disk space.

Back to top

Is there a recommended length for tests?

Although there is no formal limit regarding test length, we recommend dividing your tests into actions and that you use reusable actions in tests, whenever possible. An 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

See also: