Welcome
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.
Integrations in UI Test perspective
In this section, you will learn about the supported integrations for the Web UI Test perspective.
Testing with EGit
You can store your test assets in the remote Git repository and use EGit for version control operations. EGit is an Eclipse plugin for the Git version control system.
Techniques for troubleshooting issues in EGit
You might encounter issues while working with EGit in HCL DevOps Test UI (Test UI). You can find the information about certain issues and how to resolve them.

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.
- Installation
  You can find information about the installation of HCL DevOps Test UI (Test UI).
- License management
  Licensing for HCL DevOps Test UI (Test UI) is administered through HCL Software License & Download portal. This portal is a FlexNet-based web application that helps to manage software entitlements and licenses.
- Starting DevOps Test UI from the command line
  You can start HCL DevOps Test UI (Test UI) from the desktop environment or a command-line interface.
- Software configuration management
  You can integrateHCL DevOps Test UI (Test UI) with the software configuration management systems to maintain an auditable and repeatable history of your organization's test assets.
- Integrations in UI Test perspective
  In this section, you will learn about the supported integrations for the Web UI Test perspective.
  - Integration plugin compatibility matrix
    You can find information about the versions of the integration plugins that are required to integrate Jenkins, Ant, and HCL DevOps Deploy (Deploy) with HCL DevOps Test UI (Test UI).
  - Testing with Ant
    You can use Ant to run compound tests and Web UI tests from the command-line interface.
  - Testing with Azure DevOps for UI tests
    When you use Azure DevOps for continuous integration and continuous deployment of your application, you can create tests for your application in HCL DevOps Test UI (Test UI) and run those tests in Azure DevOps pipelines. You can integrate Azure DevOps with Test UI by using the HCL DevOps Test Workbench (Test Workbench) extension that is available in the Visual Studio Marketplace portal.
  - Testing with EGit
    You can store your test assets in the remote Git repository and use EGit for version control operations. EGit is an Eclipse plugin for the Git version control system.
    - Importing test assets from the remote Git repository
      You can import the test assets from the remote Git repository to HCL DevOps Test UI (Test UI) and run it to test the performance of the application.
    - Pulling the changes from the remote Git repository
      You must make your local repository up-to-date by pulling the latest changes in the remote Git repository before you committ and push your updated test assets to the Git repository.
    - Publishing test assets to the remote Git repository
      When you create or update any test assets in HCL DevOps Test UI (Test UI), you can publish your changes to the remote Git repository. Therefore, when you publish test assets, other members in the project can use your test assets in their test run, if required.
    - Techniques for troubleshooting issues in EGit
      You might encounter issues while working with EGit in HCL DevOps Test UI (Test UI). You can find the information about certain issues and how to resolve them.
      - Error: Missing library files in the project
        After you pull a project in the Git perspective, Project is missing the required Library error is displayed in the Verify Problems tab. This error occurs due to the .classpath file which is specific to a workspace or system. The .classpath file needs to be pointed to the newly imported location.
      - Git merge conflicts
        Web UI test projects contain certain metafiles and test assets in binary form. When you work in a collaborative test creation environment, you might encounter Git merge conflicts while you commit test assets to the remote Git repository.
      - Conflict management: errors in assets.xml
        In a collaborative work environment, the merge conflicts in assets.xml arise despite best efforts when you pull the changes from the remote upstream.
      - Conflict management: errors in test assets
        When multiple users edit and commit the same set of test assets, then while you pull or push changes to the remote Git repository, a merge conflict occurs.
  - Configuration of test runs as a GitHub Actions Workflow
    You can configure test runs of test resources that are in a project repository of HCL DevOps Test UI (Test UI) in a GitHub Actions Workflow. You can choose to run test resources that are in the project in the GitHub Workflow when you want to run the test resources without opening the Test UI.
  - Testing with IBM® Engineering Workflow Management
    You can manage test assets with Jazz™ source control management by integrating the test workbench with IBM® Engineering Workflow Management (formerly known as Rational® Team Concert™) Eclipse client.
  - Testing with Engineering Test Management
    You can integrate IBM® Engineering Test Management (formerly known as IBM Rational® Quality Manager) with HCL DevOps Test UI (Test UI) to initiate test runs from Engineering Test Management.
  - Testing with Jenkins
    You can use the DTUI-UITest-Jenkins-HCL plugin to run tests on a Jenkins server.
  - Testing with Maven
    Starting from 9.2.0, you can use the Maven plug-in that is provided with the testing product to run tests as part of your Maven build. Apache Maven is a software build tool based on the concept of a project object model (POM).
  - Testing with Micro Focus ALM
    You can integrate HCL DevOps Test UI (Test UI) with Micro Focus Application Lifecycle Management (ALM) to run test assets from Micro Focus ALM.
  - Testing with DevOps Test Integrations and APIs
    You can use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) extension to run API tests from HCL DevOps Test UI (Test UI). You can either import the projects from Test Integrations and APIs or manage them from Test UI by establishing the connection between the products. You can also create a compound test to run the tests by using the Agents.
  - Testing with HCL® DevOps Deploy
    You can integrate HCL DevOps Test UI (Test UI) with HCL DevOps Deploy (Deploy) to run tests as a Process from Deploy.
  - Testing with IBM® DevOps Deploy
    With the HCL DevOps Test UI (Test UI) plugin for IBM® DevOps Deploy (Deploy), you can automate the execution of tests and compound tests.
- Integrations in Functional Test perspective
  In this section, you will learn about the supported integrations for the Functional Test perspective.
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.

Techniques for troubleshooting issues in EGit

You might encounter issues while working with EGit in HCL DevOps Test UI (Test UI). You can find the information about certain issues and how to resolve them.

Warning: When you initialize a new Git repository for a project in an Eclipse perspective, a .gitignore file is created in the project folder. While you commit the contents of a project to the Git repository, the .gitignore file ignores the report files. You can specify additional file types in the .gitignore file so that those file types are ignored when you commit the project contents to the Git repository.

The following topics provide more information about EGit integration issues, their causes, and the resolutions to fix the issues while you work with the Git perspective in Test UI.