Installation guide

This section includes instructions for installing OpenText Functional Testing for Developers on the different supported environments, as well as post-installation and uninstall procedures.

Prerequisites

System requirements

Ensure that your computer meets all system requirements listed in the Support Matrix.
Required permissions

Ensure that you have the required permissions on the computer. See Required permissions.
Before installing

Perform all of the following:

  • Install a supported version of Node.js (for supported versions, see the Support Matrix)

    If Node.js is not installed, you are prompted to stop the installation, install Node.js, and then start the installation again.

    To verify that Node.js is installed on the machine, run the following command with the same user used for the installation:

    node -–version

    This command returns the Node.js version installed on the machine.

    (Windows only) If the command fails to return a version number, make sure that node.exe is defined in the PATH environment variable.

    If Node.js is not found during a silent installation, the silent installation fails.

  • (Linux only) Make sure that the libgconf-2-4 package is installed.

    This package is not required for the installation to succeed, but must be installed to run the runtime engine, Object Identification Center, and Test Recorder.

  • Secure installation:

    This product can potentially be used to record network communications. Therefore, it is strongly recommended that you run the product on dedicated test machines that do NOT contain or provide access to sensitive information. In addition, you should thoroughly review your lab network topology and access permissions before using this product.

    For more details on using OpenText Functional Testing for Developers in a secure manner, review the OpenText Functional Testing for Developers Security Reference.
IDEs

If you intend to use OpenText Functional Testing for Developers from within your IDEs, make sure your IDEs are already installed.

The installation includes an IDE plugin you can install on your IDE.

The IDE plugin is currently available for Visual Studio (Windows only), Eclipse, Spring Tool Suite, JBoss Developer Studio, IntelliJ IDEA, and Android Studio.

Eclipse Kepler/Luna users:

To use the Eclipse IDE for Java EE Developers or Eclipse Standard editions with the IDE plugin, you must deploy the Google Gson plugin to your Eclipse folder:

  1. Download the Google Gson plugin, version 2.1 or later, from the MVN Repository.

  2. Copy the downloaded .jar file to your <Eclipse deployment>\plugins folder and reopen Eclipse.

For more details, see the Support Matrix.
AI-based testing

To use AI Object Detection capabilities, make sure you have the following prerequisites before installing:

  • A 64-bit operating system, Windows 8 or later.

  • The required Windows feature, depending on your Windows operating system:

    • Windows OS - Microsoft Media Feature Pack

    • Windows Server 2012 and later - Microsoft Media Foundation

    For instructions on enabling Windows features, see the Microsoft documentation.

Back to top

Enterprise deployment

When installing in an enterprise business model across many computers in a network or company, note the following:

Administrative permissions
  • Windows: Make sure you have administrator permissions on each of the computers on which you are installing.
  • Linux/Mac: Make sure you have ROOT permissions on each of the computers on which you are installing.
  • Make sure you have access to the necessary folders, files, and registry keys. For details, see Required permissions.
User Account Control (UAC) (Windows only)

You can perform the installation with User Account Control (UAC) turned on or off.
Silent installation

(Windows and Linux only)

You can perform the installation silently, including prerequisite software if needed, on a local or remote computer. For details, see:

Windows: Silent installation

Linux: Silent installation

Back to top

Required permissions

Make sure the required permissions are defined on your computer.

Note: Read/write permissions to these folders must also enable permission to any subfolders.

If not, the system administrator must grant administrative permissions to the subfolders contained in these folders.

Function Permission Item
File system permissions required for working with the product

Full read and write permissions

  • C:\Temp folder

  • The folder to save tests or run results

  • User Profile folders

  • <Windows>\mercury.ini file

  • %localappdata%\LeanFT\

  • %appdata%\OpenText folder

  • %programdata%\OpenText folder

  • %localappdata%\OpenText folder

Read permissions

Windows folder and System folder
Registry key permissions required for working with the product Full read and write permissions

  • Keys under:

    HKEY_CURRENT_USER\Software\Mercury Interactive

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hewlett-Packard

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Mercury Interactive

    Note: on 32-bit computers, omit the WOW6432Node key from the paths.

  • Keys under HKEY_CURRENT_USER\SOFTWARE\Hewlett-Packard
Read and Query Value permissions

All HKEY_LOCAL_MACHINE and HKEY_CLASSES_ROOT keys

Permissions to work with ALM

 Full read and write permissions

  • ALM cache folder

  • <Program Data>\HP folder
Permissions to work with BPT Miscellaneous

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

    Tip: The Modify Component permission enables you to work with component properties (the fields in the component Details tab). You do not need this permission to work with component steps.

  • To work with parameters in ALM, you must have all the parameter task permissions set in ALM.

  • To modify application areas, you must have all of the separate permissions for resources required for modifying components, and adding, modifying, and deleting steps. If one of these permissions is not assigned, the application areas open in read-only format.
Function Permission Item
File system permissions required for installing the product

Full read and write permissions
  • ROOT
  • /opt(install location)
  • /var(installer registry file)
  • IDE folders (dropins/plugins)
  • /opt/google/chrome (chrome extension)
File system permissions required for working with the product Full write permissions

home directory
Full read permissions
  • /opt/uftdeveloper
  • IDE folders

To work with application models in Eclipse on Linux, you must start Eclipse as a root user.

Function Permission Item
File system permissions required for installing the product Full write permissions
  • /Applications
  • IDE location
File system permissions required for working with the product

Full read and write permissions
  • User folder
  • IDE location

MacOS Ventura or later

To automatically install the IDE plugins as part of the installation, your Mac must allow Full Disk Access for Java processes.

Caution: Consult your company's security policies before changing this setting.

Once the installation is complete, you may restore this Privacy and Security setting to its previous value.

If you do not have Full Disk Access allowed for Java processes, you can manually install the IDE plugins once the installation is complete.

Back to top

Help improve the product

You can help us improve the quality, reliability, and performance of OpenText Functional Testing for Developers by participating in the improvement program. The data you provide helps us understand which improvements matter most.

When you join the program, anonymous information is collected about your software and hardware configuration, and about how you use OpenText Functional Testing for Developers.

The following information is not collected:

  • Your name, address, or any other personally identifiable information

  • Specific information about your environment, servers, or applications

  • The code from any of your scripts

Note: Participating in this program does not degrade the performance of your software, and does not add you to contact lists for any sales offers.

How do I join or leave the program?

During installation

  • If you use the installation wizard, select or clear this checkbox on the license agreement screen: Participate in the UFT Developer improvement program

  • If you install silently on Windows or Linux machines, you can opt out of this program by using the relevant command option. See the silent installation details in Install on Windows or Install on Linux.

After installation

You can join or leave the improvement program from the runtime engine settings.

Select or clear the option: I want to help! Collect anonymous feature usage data. For details, see Customize the runtime engine settings or Configure the grid's runtime engine settings.

Back to top

See also: