Test Design StudioGo to Previous Topic: Adding Custom Code Snippets to FoldersGo to Next Topic: Build Process

Interacting with Unified Functional Testing

Summary

Test Design Studio is a companion to Unified Functional Testing (UFT) and not a replacement. While Test Design Studio allows you to more efficiently perform many of the tasks that would otherwise require the use of UFT, Test Design Studio will never be a replacement for the record/playback engine offered by UFT itself. When use of Unified Functional Testing is necessary, Test Design Studio offers many mechanisms to move between the two tools.

Warning:   The following interaction requires the UFT Automation Object Model API, so Unified Functional Testing must be installed on the same workstation as Test Design Studio for the following operations to work properly.

'Open in Unified Functional Testing' Command

When editing a UFT test in Test Design Studio, the Open in Unified Functional Testing command can be used to have UFT open the same file. This will allow you to quickly load a file to validate playback or adjust test settings not available from within Test Design Studio. This command is available on the context menu of a test in Solution Explorer or on the document tab of an already open test (shown in the image below).

Tip:    Test Design Studio will restart UFT with the proper add-ins before loading a test if any of the necessary add-ins are not currently loaded.
Tip:    When working with HPE Application Lifecycle Management, Test Design Studio also attempts to ensure that UFT is connected to the proper HPE Application Lifecycle Management project before opening the test.
Warning:    Be sure any unsaved modifications you made to the test in Test Design Studio are saved before opening in Unified Functional Testing since UFT can only open the last saved version of the file.

'Open Active UFT File' Command

Since Test Design Studio offers a superior editing experience over Unified Functional Testing, we have made it easy to have Test Design Studio quickly open the same test that is actively open in UFT. To do so, select File -> Open -> Active UFT File from the main menu. You will now be able to easily edit the same file without having to browse for the location.

Note:   The UFT API only provides context for Tests and BPT Components, so this command is unable to determine if you have a library open in UFT.

'Launch Unified Functional Testing' Command

To easily open Unified Functional Testing at any time, you can use the Tools -> Launch Unified Functional Testing command from the main menu.

Many automation projects require UFT to be configured a certain way in order for test objects to be configured correctly. Common practice is to create a VBScript file that launches UFT and configures the settings to match the needs of your project. Test Design Studio allows you to specify a startup script for each project that will be used to configure and load Unified Functional Testing with the proper settings for your project. This script will be executed for you when you select the Launch Unified Functional Testing command.

Our walkthrough project has already configured a startup script. It can be found in Solution Explorer by expanding the Startup Script folder and locating the StartupScript.vbs file. To view the configuration settings that established this file as the startup script, right-click on the project node (#1 in the image below) and select Properties from the context-menu (#2).

This will open the UFT Project Pages for our project.

These property pages are used to configure different elements of your project. Select the HPE UFT tab to display settings related to Unified Functional Testing.

In addition to the Startup Script setting discussed above, we can also specify the necessary add-ins for our project and any search folders to be configured. Based on many of the configuration settings specified for a project, the startup script can be automatically regenerated to reflect the current configuration. This automatic generation of the startup script is performed during the Build Process of a project, and is discussed later.