UFT program use

To check for software updates, patches, or service packs for UFT, visit the Software Support Site.


Working with UFT requires a license. When you install UFT, you select one of the following license types:

  • A permanent seat license that is specific to the computer on which it is installed (includes a 60-day demo license)

  • A network-based concurrent license that can be used by multiple UFT users

You can change your license type at any time (as long as you are logged in with administrator permissions on your computer). For example, if you are currently working with a seat license, you can choose to connect to a concurrent license server, if one is available on your network.

For information on modifying your license information, see the Unified Functional Testing Installation Guide.

Note: You can also open UFT using a legacy license, although the functionality will be limited to the service that you are licensed to use. For example, you can open UFT using a legacy QuickTest Professional or Service Test license and access GUI testing or API testing functionality.

Back to top

Required permissions for UFT

Required file system permissions


You must have read/write permissions to the following files and folders, as well as any sub-folders:

  • The Windows\System32 folder

  • The Temp folder

  • The folder containing UFT solutions, tests, or run results

  • The <Program Files>\Common Files\Mercury Interactive folder

  • The <Program Data>\HPE folder

  • User Profile folders

  • The <Windows>\mercury.ini file

  • The following AppData folders:



    %appdata%\HPE\API Testing


You must have read permissions to the following folders:

  • The Windows folder

  • The System folder

Required registry key permissions


All keys under:

  • HKEY_CURRENT_USER\Software\Mercury Interactive




Read and
Query Value

Back to top

Required permissions for ALM

Read/write permissions
  • ALM cache folder

  • <Program Data>\HP folder

  • UFT Add-in for ALM installation folder

Administrative permissions For the first connection to ALM

Back to top

Required permissions for BPT

Ensure that you have the required ALM permissions before working with business components and application areas.

Component steps

To work with component steps in ALM, you must have the appropriate Add Step, Modify Step, or Delete Step permissions set.

You do not need Modify Component permission to work with component steps.

The Modify Component permission enables you to work with component properties (the fields in the component Details tab).

Parameters in ALM or other testing tools

To work with parameters in ALM or in a testing tool, you must have all the parameter task permissions set in ALM.

Application areas

To modify application areas, you must have the separate permissions for resources required for modifying components, and adding, modifying, and deleting steps.

All four permissions are required.

If one of these permissions is not assigned, you can open application areas only in read-only format.

Back to top

Back to top

Demo applications

Many examples in this help use the Mercury Tours sample Web site. The URL for this Web site is: http://newtours.demoaut.com.

Note that you must register a user name and password to use this site.

A sample Flight Windows-based application is also provided with the UFT installation. You can access it from:

  • Start > Programs > Micro Focus > Micro Focus Unified Functional Testing > Sample Applications > Flight API or Flight GUI
  • <UFT installation folder>/samples/Flights Application/FlightsGUI.exe (for the Flight GUI application)
  • <UFT installation folder>/samples/Flights Application/FlightsAPI.exe (for the Flight API application)
  • Windows 8 and higher: C:\Program Files (x86)\Micro Focus\Unified Functional Testing

Back to top


Many operations are performed using the mouse.

In accordance with Section 508 of the W3C accessibility standards, UFT also recognizes operations performed using the MouseKeys option in the Windows Accessibility Options utility.

Additionally, you can perform many operations using shortcut keys.

Back to top

Unicode Compliancy

Unified Functional Testing is Unicode compliant according to the requirements of the Unicode standard, enabling you to test applications in many international languages.

Test non-English language applications as long as the relevant Windows language support is installed on the UFT computer.

Names and paths of tests and resources (for example, function libraries, object repositories, and recovery scenarios) are not Unicode compliant and therefore should be specified in English or in the language of the operating system.

Back to top