Welcome
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.
Functional testing proxy SDK technology samples
Functional testing proxy SDK samples are simple examples of proxy source code and applications under test (AUT).
JSpinnerProxy
This JSpinnerProxy sample explains how to extend recording behavior of a control with SubItems, and support the playback for the extended recording behavior. The sample works with the application-under-test (AUT) sample.
Examples you can use
This proxy sample explains how to extend the recording behavior of a control with SubItems and support for the corresponding playback.

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) 2024.06 (11.0.2).
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.
- Sample project to test a Java application
  The sample functional test project is created using the first few lessons of the "Create a functional test" tutorial . You can look at the test assets while you do the tutorial or after you complete it.
- Functional test project to test an HTML application
  This is a sample functional test project that contains various functional test scripts for testing an HTML application. In this sample project, the IBM® Rational® Team Concert™ web client is used as an application under test.
- Functional testing proxy SDK technology samples
  Functional testing proxy SDK samples are simple examples of proxy source code and applications under test (AUT).
  - ButtonProxy
    The ButttonProxy sample has two HCL DevOps Test UI (Test UI) proxies. There is one button control each for the Abstract Window Toolkit (AWT) and the Java foundation class (JFC). The sample works with the application-under-test (AUT) sample.
  - JFormattedTextFieldProxy
    This JFormattedTextFieldProxy sample explains how create a new proxy class add new control properties and control data. The sample works with the application-under-test (AUT) sample.
  - CheckBoxProxy
    This CheckBoxProxy sample explains how to create a new proxy class and new TestObjects and then map them to the javax.swing.JCheckBox control. The sample works with the application-under-test (AUT) sample.
  - Button OverrideProxy
    This ButtonOverrideProxy sample explains how you can extend the recording behavior of HCL DevOps Test UI (Test UI), add more properties and set up a simple value manager and value class. This sample proxy is written for the java.awt.Button control. The sample works with the application-under-test sample (AUT).
  - JSpinnerProxy
    This JSpinnerProxy sample explains how to extend recording behavior of a control with SubItems, and support the playback for the extended recording behavior. The sample works with the application-under-test (AUT) sample.
    - Examples you can use
      This proxy sample explains how to extend the recording behavior of a control with SubItems and support for the corresponding playback.
  - TreeProxy
    This TreeProxy sample explains how to extend recording behavior of a control with SubItems, and support the playback for the extended recording behavior. The sample works with the application-under-test (AUT) sample. To view the samples, you must import the tree proxy, tree application and the tree custom control for which the proxy is being written into your workspace.
- Functional testing samples for the Visual Studio IDE
  HCL DevOps Test UI (Test UI) ships with some example code you can use in your own scripts. You can open these examples from within the sample project shipped with Test UI. The sample project was created using the Test UI tutorial. For reference, you can look at the script and other test assets while you do the tutorial, or after you complete the tutorial, if you want to compare the script and test assets to your files or actually play back the script.
- Functional testing proxy SDK samples for the Visual Studio IDE
  HCL DevOps Test UI (Test UI) ships with some example proxy code you can use to learn about proxy SDK. You can open these examples from within the sample projects shipped with Test UI.
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).
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.

Examples you can use

This proxy sample explains how to extend the recording behavior of a control with SubItems and support for the corresponding playback.

Extended Capabilities: Recording controls with SubItems

This proxy sample extends the processSingleMouseEvent() proxy API to modify the recording behavior of a spin control. Although a spin control has two buttons and one text control as its children, from a testing perspective it must be treated as a single control with no children appearing in the TestObject Map. (In the TestObjectMap, the buttons and the text are treated as SubItems.) The processSingleMouseEvent() implementation sets methods with suitable SubItems, for example atButton("UP") or atButton("DOWN") as parameters for recording. Also note that although there are child objects for the spin control, you must make sure they are not listed as separate TestObjects. Therefore, the getChildAtPoint() and getChildren() APIs are extended to return null values. These child objects are treated as SubItems.

Playback Support

To support playback for each SubItem that is introduced during recording, HCL DevOps Test UI (Test UI) looks for the screen rectangle for each SubItem through the proxy. The SubItem rectangle can be provided by extending java.awt.Rectangle getScreenRectangle(Subitem subitem) proxy API.

Deploy the binaries

Copy the JSpinnerProxy.jar and JSpinnerProxy.rftcust files to the customization directory and restart Test UI to test the sample application-under-test (AUT).

Verify the recording behavior

You can verify the recording behavior of the spin control:

Before you deploy the proxies, when you record results of the up and down buttons of JSpinner, the clicks are recorded as button.click(), where each up and down control is treated as a separate control.
After you deploy the proxies, clicking on the up button is recorded as spinner().click(atButton("UP")). Notice that the buttons are treated and recorded as SubItems and not as separate TestObjects.

Verify the playback behavior

Before you deploy the proxies, playing back user actions with SubItems, for example spinner().click(atButton("UP")) throws an exception, Point not found.
After you deploy the proxies, playing back user actions with SubItems work fine.