Welcome
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.
Tests in the UI Test perspective
When you develop web applications, Windows-based applications, or mobile applications, you can use HCL DevOps Test UI (Test UI) to create functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
Compound tests
You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.

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.03 (11.0.1).
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.
- Tests in the UI Test perspective
  When you develop web applications, Windows-based applications, or mobile applications, you can use HCL DevOps Test UI (Test UI) to create functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
  - Web UI tests
    You can test web applications in HCL DevOps Test UI (Test UI) by using the industry-standard browsers such as Google Chrome, Apple Safari, Mozilla Firefox, and Microsoft Edge. You can record Web UI tests and then play back the tests to evaluate the test results. You can also test the web applications on dual monitors when you extend the display of your computer to a secondary monitor.
  - Mobile tests
    You can test the Android or iOS mobile applications by recording and playing back mobile tests on Android devices or emulators, iOS mobile devices or simulators by using HCL DevOps Test UI (Test UI).
  - Windows tests
    You can configure the Windows applications to record and play back tests on the Windows desktop applications. You can also test the Windows applications on dual monitors when you extend the display of your computer to a secondary monitor.
  - SAP tests
    When you record a test, the test creation wizard records your interactions with the SAP server, generates a test from the recording, and opens the test for editing. You can record tests from the SAP GUI. You can also record SAP batch input tests that can be used to produce a heavy load on the server while minimizing the processing requirements for virtual testers.
  - Selenium or Appium tests
    You can manage your Selenium or Appium Java™ tests from the UI Test perspective, where you can import and modify the tests, add them to compound tests, and run them. You can also create new Appium Java tests from the Perfecto perspective on Windows™ and Mac OS, add the tests to compound tests, and run them. Perfecto is not currently supported on Linux®.
  - Compound tests
    You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
    - Creating a compound test
      You can create a compound test to organize smaller tests into scenarios that can be run simultaneously or sequentially. You can combine various tests to speed up and minimize the test effort.
    - List of compound tests
      You can view the list of compound tests in the Test Navigator.
    - Adding tests into a compound test
      After creating a compound test, you can add the smaller test components that contribute to the larger workflow you are constructing with the compound test. When you run a compound test, each of the tests added to it are run in the sequence defined.
    - Modifying a compound test
      You can modify a compound test in the Compound Test Editor.
    - Importing an existing compound test into a project
      You can import a compound test into a project.
    - Running compound tests
      You can run a compound test that is configured in the UI Test perspective. The test elements are run in the order that is defined in the compound test.
    - Generating compound test result reports
      When a compound test run is completed, a Test Log is shown in the Test Execution perspective. You can work with the information in the test log and also generate test result reports.
  - Accelerated Functional Tests
    When you create Web UI, mobile, or Windows tests, you can use the Accelerated Functional Test (AFT) feature in HCL DevOps Test UI (Test UI) to distribute test effort during the play back of the recorded tests.
  - Keywords
    In HCL DevOps Test UI (Test UI), you can record and then associate Test Workbench tests with the keywords that are created in IBM® Engineering Test Management. The keywords are used in manual tests in Engineering Test Management. When you run a manual test that contains a keyword associated with a HCL DevOps Test Workbench (Test Workbench) test, the Test Workbench test is run on the workstation where the adapter has been started.
- Tests in the Functional Test perspective
  When you develop Java, HTML, or Terminal-based applications, you can use HCL DevOps Test UI (Test UI) to create traditional functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.
- Extending the UI Test perspective with custom Java™ code
  You can use custom code to extend the default Web UI testing capabilities. You can write custom Java™ code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
- Extending the Functional Test perspective
  You can use custom code to extend the default functional testing capabilities. You can write custom code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.
- Extending the functionality in the Visual Studio IDE
  These topics describe various ways that you can customize HCL DevOps Test UI (Test UI) or use the application programming interface (API) to extend Test UI functionality.
- Experimental features
  HCL DevOps Test UI (Test UI) contains a set of pre-releases that enable you to test various experimental features. These experimental features, while still in progress, are introduced early in the release to seek your feedback on its overall functionality and performance. You can play around with these capabilities before they are made available and supported as a general feature in an upcoming release.
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.

Compound tests

You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.

If you need to combine various tests into a single workflow or end-to-end scenario, you can organize the tests into a compound test. Each test may perform a part of the scenario. Each test may also run in a different domain, for example, different web browsers. A typical example of a compound test is an online buying workflow. You may have built smaller tests for each part of an online purchase transaction, such as "log on", "log out", "view item", "add to cart", and "check out". You can combine these tests into a single flow in a compound test. When the compound test is run, its individual tests are run in sequence.

The types of tests you can combine into a compound test depend on the testing capabilities you have purchased. You can also shell-share HCL DevOps Test Workbench (Test Workbench) family products to add multiple tests into a compound test.

To build the scenario you require in a compound test, you can also add the following annotations:

Comments
Synchronization points
Loops
Delays
Transaction folders
IF-THEN-ELSE
Tests that are mandatory, using the Finally blocks
Tests to be run in random order, using the Random Selector