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 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.
Editing a test that uses application designs
You can edit the Web UI tests that were created by using the application designs to add any missing details or actions as required.

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.
    - 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.
      - Adding a web application design
        When you want to create tests for web applications that are in the early stages of development, you can do so by adding designs of the applications. You must first upload the images of wireframes as part of the application configuration process. You can use these configured applications that are associated with their wireframes to generate tests through recording.
      - Editing a web application design
        When you upload the designs of the web applications that are in the early stages of development, HCL DevOps Test UI (Test UI) identifies the common UI controls on the application designs. You can review the controls that are identified on the designs and validate them in the design editor. You can then edit the type and label of the identified controls as required on each page.
      - Editing the web application configuration
        When you want to add more designs of the configured application, delete the uploaded designs, or want to edit the details of the application, you can do so in the Edit web application window.
      - Recording a Web UI test by using application designs
        You can generate a Web UI test from the UI Test perspective by recording the user actions on the application designs that are configured on the Application Configuration page.
      - Editing a test that uses application designs
        You can edit the Web UI tests that were created by using the application designs to add any missing details or actions as required.
      - FAQs: Design driven testing
        You can find answers to a few generic questions about the design driven testing (DDT) feature in the UI Test perspective.
  - 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.

Editing a test that uses application designs

You can edit the Web UI tests that were created by using the application designs to add any missing details or actions as required.

Before you begin

You must have completed the following tasks:

Recorded a Web UI test by using the configured application designs. See Recording a Web UI test by using application designs.
Read and been familiar with the addition of user actions in a test. See Adding user actions in a test.

Procedure

Open a Web UI test that was created by using the configured application designs.
Check all the test steps to verify whether the object, action, and the associated content or label are correct.
You can modify the following values for an object:
- Graphic object
- Object's action
- Object identified by
  Notes:
  
  If an object is identified by Xpath, you must change the identifier from Xpath to a visibly identifiable property such as Content and then provide the value in the text box.
  
  If a control has an image associated with a label, then the control is identified as an image rather than the actual control type. Before running the test, you must edit the control type to assign the correct property.
Add steps for any missing user actions in the test.
You can add user actions in the Test Contents area or from the SmartShot view.
Click the Launch application node in the Test Contents area and update the application URL in the Application Details pane as required.
Save the test.

What to do next

You can perform the following actions:

Run the test if the web application is deployed and available to run. You must enable self healing or guided healing when you run the test to update the test with the actual screens of the application. See Running a Web UI test.
Update the test by using the collected data after you run the test. See Updating tests by using the guided healing feature.