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.
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.
Techniques for troubleshooting issues in EGit
You might encounter issues while working with EGit in HCL OneTest™ Performance. You can find the information about certain issues and how to resolve them.
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.

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
    You can use Ant to run compound tests and performance tests from the command-line interface.
  - 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.
  - 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.
    - Importing test assets from the remote Git repository
      You can import the test assets from the remote Git repository to HCL OneTest™ Performance 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 OneTest™ Performance, 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 OneTest™ Performance. 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
        Performance 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.
  - 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
    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.
  - 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 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).
  - Integrating and running performance test scripts in Micro Focus ALM
    You can integrate Micro Focus Application Lifecycle Management (ALM) by using a readily available template from the installation directory of HCL OneTest™ Performance to run performance test scripts and obtain test result details.

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.

The project includes a metafile called assets.xml that contains a list of all test asset files in a project along with their dependencies in an XML format. The assets.xml file is automatically generated by HCL OneTest™ Performance from the contents of the project. The assets.xml file is refreshed each time you modify the files in the project. These changes in the assets.xml file are the most common source of merge conflicts.

The following image displays the merge conflicts when you attempt to perform a pull request on the local Git repository by using the Git perspective:

merge_conflict

You can perform the following steps to resolve the merge conflicts in the assets.xml file:

Click Close to dismiss the merge conflict result dialog box.
Click Window > Show View > Other.
Expand Git, and then select Git Staging.
Click Open.

The conflicting files are displayed in the Unstaged Changes pane.
Right-click the project from the Test Navigator pane, and then click Refresh.

When you refresh the project, the assets.xml file is updated to include the local files in the project and also files that were pulled down from the remote upstream.
Go to the Git Staging view, and then move the files from Unstaged Changes to Staged Changes by using the Add selected files to the index or icon.
Enter a message in the Commit Message pane, and then click Commit and Push.

The Push Result dialog box is displayed with the status of the commit to the remote Git repository.