Home
Administrator Guide
This guide describes how to install HCL OneTest™ Performance. 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.
Integration with other products
You can integrate HCL OneTest™ Performance with certain products to run tests, manage test assets, and create defects.
EGit integration
EGit is an Eclipse plugin for the Git version control system. You can store your test assets in the Git repository and use EGit for the daily version control operations.

Administrator Guide
This guide describes how to install HCL OneTest™ Performance. 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 of HCL OneTest™ Performance
  Installing the product involves verifying requirements, planning, managing licenses, and configuring web-based help. This section lists all such topics.
- License management
  Licensing for your HCL software is administered through HCL® License & Delivery portal. This portal is FlexNet-based web application to manage software entitlements and licenses.
- Product upgrade and migration
  When you want to use the enhanced functionalities of HCL OneTest™ Performance Rational® Service Tester for SOA Quality, 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.
  - Testing with Ant
    You can use ant to run performance and compound tests from the command line. Starting from V2.0.0 of the ant plugin, you can run multiple tests simultaneously. V5.0 of the ant plugin is supported in HCL OneTest™ Performance V10.0.2 of the testing products.
  - 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. You can integrate Azure DevOps with HCL OneTest Performance by using the HCL OneTest Studio extension that is available in the Visual Studio Marketplace portal.
  - Integrating with Apache JMeter
    Starting from 9.5, you can use JMeter tests extension with HCL OneTest™ Performance HCL OneTest Performance to execute JMeter tests.
  - EGit integration
    EGit is an Eclipse plugin for the Git version control system. You can store your test assets in the Git repository and use EGit for the daily version control operations.
  - Integration with IBM® 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
    When you use HCL Launch for automating application deployments of your application, you can create tests for your application in HCL OneTest™ Performance and run those tests in HCL Launch by using the HCL OneTest Performance Launch plugin.
  - Testing with HCL OneTest™ API
    Starting from V9.1.1, you can use HCL OneTest™ API extension to execute API tests. In 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. In HCL OneTest Performance, you can create a schedule or compound test to run the IntegrationAPI tests by using the Agents.
  - Integration with IBM® UrbanCode™ Deploy
    When you use UrbanCode™ Deploy (UCD) for automating application deployments of your application, you can create tests for your application in HCL OneTest™ Performance and run those tests in UrbanCode Deploy by using the HCL OneTest Performance UCD plugin.
  - 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.
  - Testing with Jenkins
    You can use the HCL OneTest™ Performance Jenkins plugin for performance testing to run tests on a Jenkins server by using a Jenkins build step.
  - Testing with Maven
    Starting from V9.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).
  - Integrating and running performance test scripts in Micro Focus ALM
    To obtain test result details, you must integrate and run performance test scripts in Micro Focus Application Lifecycle Management (ALM) by using a readily available template available in HCL OneTest™ Performance installation directory.

EGit integration

EGit is an Eclipse plugin for the Git version control system. You can store your test assets in the Git repository and use EGit for the daily version control operations.

When you install the product, by default EGit is part of the product. To avoid the clutter, EGit is a separate Eclipse perspective in the product. For more information about EGit, read its documentation.

Open perspective dialog

In Eclipse perspective, when you initialize a new Git repository for a project, a .gitignore file is created in the project folder, by default. While committing the contents of a project to Git, the .gitignore file ignores the report files.

Note:

After you pull a project in Git perspective, 'Project is missing required Library' error appears in the Verify Problems tab. This error occurs due to the .classpath file which is specific to a workspace or system and needs to be pointed to the newly imported location. To resolve this issue:
1. Under Package Explorer, from the required project, navigate to Java Build Path > Libraries.
2. Delete all the jar files that are missing after the pull. These files are marked with a red cross.
3. Playback the project. The required jar files are added to the project.

You can also specify additional file types in the .gitignore file so that these file types are ignored while committing the project contents to Git.