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.
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.
Creation of Web UI tests
HCL DevOps Test UI (Test UI) provides multiple ways to create Web UI tests using the UI Test perspective. You can create a Web UI test that captures both functional and HTTP traffic in the same recording. In addition, you can create a Web UI test for a web application that is already running in an instance of the Chrome, Firefox, or Safari browser. You can also initiate a recording from a step of an existing test. You can also play back tests on Microsoft™ Edge browser but they must be recorded on Chrome, Firefox, or Internet Explorer.
Recording steps for an existing Web UI test
If you already have a test, you can add more steps to it at a desired location by initiating the recording from a step or from the application node. For instance, if the task flow has changed in the new version of the application that you recorded and you want to update the existing test script, start the recording from the step after which the new steps must be added. You can also initiate the recording from the Launch application or In application nodes of the test.

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.
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.
    - Creation of Web UI tests
      HCL DevOps Test UI (Test UI) provides multiple ways to create Web UI tests using the UI Test perspective. You can create a Web UI test that captures both functional and HTTP traffic in the same recording. In addition, you can create a Web UI test for a web application that is already running in an instance of the Chrome, Firefox, or Safari browser. You can also initiate a recording from a step of an existing test. You can also play back tests on Microsoft™ Edge browser but they must be recorded on Chrome, Firefox, or Internet Explorer.
      - Prerequisites for creating tests
        Before you can create a test, you must complete the prerequisite tasks.
      - Recording a Web UI test
        You create a Web UI test in the UI Test perspective. HCL DevOps Test UI (Test UI) automatically enables web browsers and configures the test environment before you start recording tests for web applications.
      - Recording a Web UI test by using a running browser instance
        You can create a Web UI test of a web application from the UI Test perspective using a browser that is already running locally. For example, if you have already recorded some part of a web application, you can go back at a later time to resume the recording. Support is provided for Chrome and Firefox on Windows and Linux computers and for Safari, Chrome and Firefox on Macintosh computers. Internet Explorer is not supported.
      - Recording steps for an existing Web UI test
        If you already have a test, you can add more steps to it at a desired location by initiating the recording from a step or from the application node. For instance, if the task flow has changed in the new version of the application that you recorded and you want to update the existing test script, start the recording from the step after which the new steps must be added. You can also initiate the recording from the Launch application or In application nodes of the test.
      - Recording a Web UI test immediately after the previous playback
        When you want to continue the testing after the previous playback, you can choose to record a new Web UI test by using the Allow recording after playback option.
      - Recording a test with Google Chrome Device Mode
        You can use the Google Chrome Device Mode feature to emulate tests of web applications on mobile devices.
      - Annotating a test during recording
        You can add comments, add transactions, or change a page name while you record a test. The advantage of adding these elements during (rather than after) recording is that you can place the annotations in the test exactly where you want. In addition, because annotations are part of the recorded test, they are regenerated when you regenerate the test. You can also insert split points into a test during record.
      - Splitting a test during recording
        You can insert split points when you record a test. Split points allow you to generate multiple tests from a single recording that you can replay in a different order with a schedule.
      - Putting test assets under source control
        Use version-control software, such as Rational® Team Concert™, to put the test assets under source control.
    - Modification of Web UI tests
      With the test editor, you can view and customize a Web UI test.
    - Creation of design driven tests
      You can start the testing phase in the early stages of the development of web applications by using design driven testing (DDT). DDT is a dynamic feature that leverages machine learning capabilities to create tests by using the designs of web applications under development.
  - 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.
  - 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.

Recording steps for an existing Web UI test

If you already have a test, you can add more steps to it at a desired location by initiating the recording from a step or from the application node. For instance, if the task flow has changed in the new version of the application that you recorded and you want to update the existing test script, start the recording from the step after which the new steps must be added. You can also initiate the recording from the Launch application or In application nodes of the test.

Procedure

Open the test script in which to add steps from a new recording.
Right-click the step after which the new steps must be added and click Insert > Steps from Recording (web).
You can also start the recording from the "Launch application", "In application", and "Window" nodes of a test script. To do that, right-click the node and click Add > Steps from Recording (web).
In the Select Client Application page of the recording wizard, select a web browser or click Running Browser Instance. Click Next.

When you select a browser, Test UI configures and starts the browser for you to start the recording from the first page of the application. When you select Running Browser Instance, you start recording the application that is already running in a browser from the current state of the application so that you do not need to start recording from the first page of the application.
Complete one of the following steps:
1. If you selected a web browser, follow the next set of instructions in Recording a Web UI test.
2. If you selected Running Browser Instance, follow the next set of instructions in Recording steps for an existing Web UI test.
After the recording is done, the test is generated. Click Close. The newly recorded steps are added after the step from where you initiated the recording. If you initiated the recording from the application node, the new steps are added after the application node or after the last step in the application node. All the new steps are highlighted. To save the changes, click Save.

What to do next

You can enhance the test. See Modification of Web UI tests.