Welcome
Test Execution Specialist Guide
This guide describes how to automate the playback of the tests by using different methods such as Docker, IBM Cloud Private, Jenkins and so on. The test results can be pushed to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel).
Configuration of test runs from the Functional Test perspective
When you created functional tests, you must configure the run of the recorded functional tests from the Functional Test perspective before you can view the test results.
Running tests for a running Java application
You can run a functional test for a Java application that is already running locally. You can configure the environment variable JAVA_TOOL_OPTIONS that enables Test UI to detect an already running application instance and run the test on it.

Release Notes
This document includes information about the new features introduced, features deprecated or removed, defects fixed, and known issues identified in this version of HCL DevOps Test UI (Test UI). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System Requirements
This document includes information about hardware and software requirements for HCL DevOps Test UI (Test UI) 2025.12 (11.0.7).
Getting Started Guide
This guide provides an overview of HCL DevOps Test UI (Test UI). You can find the task flows to get you started with Test UI. This guide is intended for new users.
Tutorials
You can learn to start using Test UI by reviewing the information in the Tutorials for the UI Test perspective and Functional Test perspective.
Samples
You can find the sample project that you can use with HCL DevOps Test UI (Test UI) to test the functionality of an application.
Administrator Guide
This guide describes how to install HCL DevOps Test UI (Test UI) software. After you install the software, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
Test Author Guide
This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
Test Execution Specialist Guide
This guide describes how to automate the playback of the tests by using different methods such as Docker, IBM Cloud Private, Jenkins and so on. The test results can be pushed to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel).
- Configuration of test runs from the UI Test perspective
  When you create Web UI, mobile, or Windows tests, you must configure the play back of the recorded tests as test runs from the UI Test perspective before you can view their test results.
- Configuration of test runs from the Functional Test perspective
  When you created functional tests, you must configure the run of the recorded functional tests from the Functional Test perspective before you can view the test results.
  - Script Playback
    When you play back a script, HCL DevOps Test UI (Test UI) replays your recorded actions, which automates the software testing cycle.
  - Restoring the test environment before playback
    The state of both the environment and the application-under-test can affect script playback. If the recorded environment and the playback environment are different, playback problems can occur.
  - Configuring how to handle unexpected windows during playback
    Problems can occur during script playback if unexpected windows are displayed. Unexpected windows such as security and warning message dialogs or custom dialogs can cause playback failure with exceptions such as object not found or window not activated. You can configure how unexpected windows can be handled so that scripts can be played back smoothly without interruption.
  - Inserting dynamic test objects
    You can also insert dynamic test objects by using Insert Dynamic Test Object. The hierarchy of a test object in the object map represents the order of search of the particular control during playback. Over a series of application changes, the hierarchy of the objects may change if new objects are introduced in the test application. This results in a playback failure. Using dynamic test objects you can anchor a test object as a descendant to its parent.
  - Enabling the dynamic find feature
    The test object map lists in a hierarchy the test objects in the application under test. Changes to the application-under-test might result in changes in the object hierarchy. During playback, HCL DevOps Test UI (Test UI) is then unable to find an object whose hierarchical position has changed, and this causes playback failure. With the dynamic find feature you can prevent playback failure that results from hierarchy changes in the application under test. The dynamic find feature performs searches for objects whose hierarchy has changed, when a search that is based on object recognition scoring (ScriptAssure) fails to find such objects.
  - Enabling the dynamic find feature in the Visual Studio IDE
    The HCL DevOps Test UI (Test UI) test object map lists the test objects in the application under test, in a hierarchy. Changes to the application under test might result in changes in object hierarchy. During playback, Test UI is unable to find an object whose hierarchical position has changed, and this causes playback failure. With the dynamic find feature, you can prevent playback failure that results from hierarchy changes in the application under test. The dynamic find feature performs searches for objects whose hierarchy has changed when a search based on object recognition scoring (ScriptAssure) fails to find such objects.
  - Using ScriptAssure
    Using ScriptAssure™, you can play back scripts successfully even when the application-under-test has been updated.
  - Ambiguous object recognition in functional testing
    Ambiguous recognition occurs when HCL DevOps Test UI (Test UI) can not uniquely identify an object in the system-under-test. This commonly happens when Test UI cannot differentiate between an instance of the application-under-test started by a script playback and an instance of the same application inadvertently left open previous to script playback. This also applies to identical windows from one application and identical HTML documents. Ambiguous recognition will cause script playback failure unless the duplicate application is closed.
  - Playback Monitor
    During playback you can view the script name, the number of the line that is executing, status icons, and a description of the action in progress from the Playback Monitor.
  - Pausing or stopping script playback
    Playback of a script can be paused or stopped.
  - Running scripts from DevOps Test UI
    You can run scripts from HCL DevOps Test UI (Test UI) so that all of your recorded actions are played back. The recorded actions include the actions that you performed to start and stop an application, add verification points, and any other actions that you performed while using the application.
  - Running tests for a running Java application
    You can run a functional test for a Java application that is already running locally. You can configure the environment variable JAVA_TOOL_OPTIONS that enables Test UI to detect an already running application instance and run the test on it.
  - Playback of test scripts for HTML applications by using the Web UI engine
    You can play back test scripts for HTML applications in web browsers by using the Web UI engine without enabling the Java environments and browsers.
  - Running a script from the Microsoft™ Edge browser
    You can use HCL DevOps Test UI (Test UI) to play back test scripts using the Microsoft™ Edge browser.
  - Debugging scripts
    You can use the same process to debug a Functional Test script as you would to debug other Visual Basic or Java™ applications. If you prefer, in HCL DevOps Test UI (Test UI), Eclipse Integration, you can debug your script in the Test UI Debug Perspective which makes it easier to start the debugger that comes with the Java Development Toolkit.
  - Screen snapshot on playback failure of functional tests
    If playback of a script causes an exception to be thrown, HCL DevOps Test UI (Test UI) takes a screen snapshot at the time of the failure. The screen snapshot is accessible through the log.
Test Manager Guide
This guide describes how to keep track of the performance of the application by evaluating the test results. Following topics cover how you can work with the test results.
Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL DevOps Test UI (Test UI).
Reference Guide
This guide describes the additional topics to gain more knowledge about HCL DevOps Test UI (Test UI).
All Guides (PDF)
You can find the link to view or download the content of the release notes, system requirements, and persona guides of HCL DevOps Test UI (Test UI) as a PDF file.
Security Considerations
You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
Notices
This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Running tests for a running Java application

You can run a functional test for a Java application that is already running locally. You can configure the environment variable JAVA_TOOL_OPTIONS that enables Test UI to detect an already running application instance and run the test on it.

Before you begin

You must have completed the following tasks:

Ensured that the required Java application (JAR file) is available on the local machine to run the test.
Commented out the Start App step in the test that you want to run.

About this task

Procedure

Add the following environment variable to the system:
JAVA_TOOL_OPTIONS=-Dsun.java2d.uiScale.enabled=false -Djavax.accessibility.assistive_technologies=com.rational.test.ft.bootstrap.Bootstrap -javaagent:"C:\Program Files\IBM\DevOpsTest\FunctionalTester\bin\javaagent\FtAgent.jar" --add-opens=java.desktop/java.awt=ALL-UNNAMED
Open the command line interface and check the Java version to confirm that the environment variable is active by running the following command:
java -version
The output displays the path of the added environment variable with the Java version information.
Start the Java application if it is not running.
Start the test run either from the GUI of Test UI or the command line.

The system detects the open application instance, and the playback starts successfully without closing or restarting the application.

Results

You have run a functional test for a Java application that is already running locally.