Installation prerequisites

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

Ensure that you have the required permissions on the computer. See Required permissions for Windows.

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.

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 Code, 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.

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.

• 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 for Windows.

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

(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

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

• 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

All HKEY_LOCAL_MACHINE and HKEY_CLASSES_ROOT keys

Permissions to work with OpenText Application Quality Management

• ALM cache folder

• <Program Data>\HP folder

• To work with component steps in OpenText Application Quality Management, 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 OpenText Application Quality Management, you must have all the parameter task permissions set.

• 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.

Full read and write permissions

• ROOT
• /opt(install location)
• /var(installer registry file)
• IDE folders (dropins/plugins)
• /opt/google/chrome (chrome extension)

home directory

• /opt/OpenTextFunctionalTestingForDevelopers
• IDE folders

• /Applications
• IDE location

Full read and write permissions

• User folder
• IDE location