Home
Administrator Guide
This guide describes how to install HCL OneTest™ 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 Functional Test perspective
In this section, you will learn about the supported integrations for the Functional Test perspective.
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 OneTest™ 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 HCL OneTest UI.
Prerequisites to run tests in a GitHub Actions Workflow
Before you configure a test run for any test resources that are in a project repository of HCL OneTest™ UI, you must complete certain tasks to run the test resources in a GitHub Actions Workflow.

Administrator Guide
This guide describes how to install HCL OneTest™ 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 OneTest™ UI.
- License management
  Licensing for HCL OneTest™ 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 HCL OneTest™ UI from the command line
  You can start HCL OneTest™ UI from the desktop environment or a command-line interface.
- Software configuration management
  You can integrateHCL OneTest™ 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.
- Integrations in Functional Test perspective
  In this section, you will learn about the supported integrations for the Functional Test perspective.
  - Integration plugin compatibility matrix
    You can find information about the versions of the integration plugins that are required to integrate Jenkins, Ant, HCL® Launch, and UrbanCode™ Deploy with HCL OneTest™ UI.
  - Testing with Ant
    You can use ant to run functional tests from the command line. Starting with version 2.0 of the ant plugin, you can run multiple tests simultaneously.
  - Testing with Azure DevOps for functional tests
    When you use Azure DevOps for continuous integration and continuous deployment of your application, you can create tests for your application in HCL OneTest™ UI and run those tests in Azure DevOps pipelines. You can integrate Azure DevOps with HCL OneTest UI by using the HCL OneTest Studio extension that is available in the Visual Studio Marketplace portal.
  - Testing with Cucumber
    Starting with HCL OneTest™ UI 9.2, you can take advantage of Cucumber integration to create, annotate, and run functional test scripts that can be easily understood by all members of the team.
  - Testing with Micro Focus Application Life Cycle Management
    To obtain test result details, you can integrate and run Functional Test scripts in Micro Focus Application Lifecycle Management by using a ready-made template available in the HCL OneTest™ UI installation directory.
  - 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 OneTest™ 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 HCL OneTest UI.
    - Prerequisites to run tests in a GitHub Actions Workflow
      Before you configure a test run for any test resources that are in a project repository of HCL OneTest™ UI, you must complete certain tasks to run the test resources in a GitHub Actions Workflow.
    - Configuring a test run in a GitHub Actions Workflow
      After you complete the prerequisite tasks to run tests in a GitHub Actions Workflow, you can configure the test run in a GitHub Actions Workflow.
  - Testing with IBM® Engineering Test Management
    HCL OneTest™ UI can be integrated with IBM® Engineering Test Management. You can execute the functional test scripts from HCL OneTest UI.
  - Testing with IBM® Engineering Test Management in the Visual Studio IDE
    HCL OneTest™ UI in the Visual Studio environment supports integration with IBM® Engineering Test Management.
  - Testing with Jenkins
    You can use the HCL OneTest™ UI - Functional Test to run tests on a Jenkins server.
  - Testing with Maven
    Starting with v9.2, you can use the Maven plug-in to run Functional Test scripts. Apache Maven is a software build tool based on the concept of a project object model (POM). You can use the Maven plug-in that is provided to run tests as part of your Maven build.
  - Testing with IBM® Engineering Workflow Management
    HCL OneTest™ UI can be integrated with IBM® Engineering Workflow Management (formerly known as Rational Team Concert). You can manage functional test assets by using the Jazz™ source control management that the Jazz Eclipse Client provides. You must have a compatible version of IBM Engineering Workflow Management server set up to use the Jazz source control management.
  - Testing with Tivoli Composite Application Manager
    HCL OneTest™ UI can be integrated with IBM Tivoli® Composite Application Manager. You can schedule the interval at which the application manager agent runs to track the response time and generate logs using HCL OneTest UI scripts.
  - Testing with HCL® Launch
    You can integrate HCL OneTest™ UI with HCL® Launch to run tests as a Process from HCL Launch.
  - Testing with UrbanCode™ Deploy
    You can run functional test scripts remotely with the HCL OneTest™ UI - Functional Test plugin for UrbanCode™ Deploy.

Prerequisites to run tests in a GitHub Actions Workflow

Before you configure a test run for any test resources that are in a project repository of HCL OneTest™ UI, you must complete certain tasks to run the test resources in a GitHub Actions Workflow.

You must be familiar with creating projects and running test resources from HCL OneTest™ UI.

You must complete the following tasks in HCL OneTest™ UI:

Created a test in the Functional Test perspective. See Testing in the Functional Test perspective.
Opened and viewed the details of the test resources that you want to run in a GitHub Actions Workflow. You must make a note of the test resource details that are in HCL OneTest™ UI.
You must note the following details of the test resource that are to be provided in the YAML file for the GitHub Action:
- The complete path of the project directory that contains test assets.
- The name of the functional test script that you want to execute.

You must complete the following tasks outside of HCL OneTest™ UI:

Create an empty Git repository on any GitHub Enterprise server, if you do not already use Git repositories to store the test resources that you create. For more information about creating Git repositories, refer to Creating a new repository.
If you are already using Git repositories to store test resources created, you can use the same repositories.
Note: You must have the required privileges in the Git repository to create a GitHub Actions Workflow.
Enable the GitHub Actions option in the Git repository, if it is not available as an option to use. For more information about enabling the GitHub Actions, refer to Learn about GitHub Actions.
Set up self-hosted runners on your computer. For more information, refer to Adding self-hosted runners.

You can continue to configure a run as a GitHub action, see Configuring a test run in a GitHub Actions Workflow.