Home
Administrator Guide
This guide describes how to install HCL OneTest™ Performance. After you install the product, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
Integration with other products
You can integrate HCL OneTest™ Performance with certain products to run tests, manage test assets, and create defects.
Configuration of test runs as a GitHub Actions Workflow
You can configure test runs of test resources that are in HCL OneTest™ Performance 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 Performance.
Prerequisites to run tests in a GitHub Actions Workflow
Before you can configure a test run for any test resources that are in HCL OneTest™ Performance, 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™ Performance. After you install the product, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Installation of HCL OneTest™ Performance
  Installation of the product involves verifying requirements, planning, managing licenses, and configuring web-based help. This section lists all such topics.
- License management
  Licensing for HCL OneTest™ Performance is administered through HCL Software License & Download portal. This portal is a FlexNet-based web application that helps to manage software entitlements and licenses.
- Product upgrade and migration
  When you want to use the enhanced functionalities of HCL OneTest™ Performance, you must upgrade to the latest version of the product software.
- Configuration of the product
  You must configure HCL OneTest™ Performance when you want to run SAP tests, collect response time breakdown data, or use the product in the Docker container.
- Integration with other products
  You can integrate HCL OneTest™ Performance with certain products to run tests, manage test assets, and create defects.
  - Integration plugin compatibility matrix
    You can find information about the versions of the integration plugin that are compatible with HCL OneTest™ Performance.
  - Running tests by using Ant
    When you want to automate repetitive tasks, you can run performance test assets from the command-line interface by using Ant.
  - Integration with Azure DevOps
    When you use Azure DevOps for continuous integration and continuous deployment of your application, you can create tests for your application in HCL OneTest™ Performance and run those tests in Azure DevOps pipelines.
  - Integration with Apache JMeter
    You can use JMeter tests extension with HCL OneTest™ Performance to run JMeter tests.
  - EGit integration
    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.
  - Configuration of test runs as a GitHub Actions Workflow
    You can configure test runs of test resources that are in HCL OneTest™ Performance 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 Performance.
    - Prerequisites to run tests in a GitHub Actions Workflow
      Before you can configure a test run for any test resources that are in HCL OneTest™ Performance, 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.
  - Integration with Engineering Test Management
    You can integrate IBM® Engineering Test Management (formerly known as IBM Rational® Quality Manager) with HCL OneTest™ Performance to initiate test runs from Engineering Test Management.
  - Integration with IBM® Engineering Workflow Management
    You can integrate Engineering Workflow Management (formerly known as Rational® Team Concert™) to create and track defects (bugs) or other work items, as a defect tracking tool in HCL OneTest™ Performance.
  - Integration with HCL® Launch
    You can integrate HCL OneTest™ Performance with HCL® Launch to run performance test assets as a Process from HCL Launch.
  - Integration with HCL OneTest™ API
    You can use HCL OneTest™ API extension to run API tests from HCL OneTest Performance. You can either import the projects from HCL OneTest API or manage them from HCL OneTest Performance by establishing the connection between the products. You can also create a schedule or compound test to run the tests by using the Agents.
  - Integration with IBM® UrbanCode™ Deploy
    You can integrate HCL OneTest™ Performance with IBM® UrbanCode™ Deploy to run performance test assets as a Process from UrbanCode Deploy.
  - Integration of Jaeger with the product
    Jaeger is software for tracing transactions between distributed services. You can use Jaeger to monitor and troubleshoot complex microservices environments.
  - Integration with Jenkins
    You can use the HCL OneTest™ Performance Jenkins 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).
  - Integration with Micro Focus ALM
    You can integrate HCL OneTest™ Performance with Micro Focus Application Lifecycle Management (ALM) to run performance test assets from Micro Focus ALM.

Prerequisites to run tests in a GitHub Actions Workflow

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

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

Created a test. See Creating tests.
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™ Performance.

You will require the following details of the test resource on your system that must be provided in the YAML file for the GitHub Action:
- The complete path to the Eclipse workspace.
- The name of the project containing the test.
- The relative path from the project to the test including the file name of the test.

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

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 Git 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.
You must be familiar with setting 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.