Release notes for HCL OneTest Performance

This document contains information about what's new, installation instructions, known issues in HCL OneTest Performance and contact information of HCL Customer Support.

Contents

Product description

You can find the description of HCL OneTest Performance.

HCL OneTest Performance is a scripting-free environment for automating load and scalability testing of web, ERP, and server-based software applications. HCL OneTest Performance provides rich and customizable reporting to help you identify the presence and cause of system bottlenecks. It captures the network traffic that is rendered when the application under test interacts with a server. This network traffic is then emulated on multiple virtual users while playing back the test. See Product overview.

What's new in 10.2.1 iFix1

This release addresses the issue of the security vulnerability in CVE-2021-44228 that is specific to Apache Log4j 2 / Log4Shell.

This release replaces HCL OneTest Performance 10.2.1 and includes all updates made in the 10.2.1 release.

These vulnerabilities are associated with the HCL OneTest Performance Apache JMeter™ Test Extension. Although the log4j libraries that are installed with the Apache JMeter Test Extension are never loaded by HCL OneTest Performance, the presence of log4j-core-2.11 might concern customers. HCL OneTest Performance 10.2.1 iFix1 removes the Apache Log4j version 2 library from HCL OneTest Performance.

If you installed HCL OneTest Performance 9.5.0 or later, you must first uninstall it, and then install HCL OneTest Performance 10.2.1 iFix1. For installation instructions, see Installation of HCL OneTest Performance.

Important: If you are using the Apache JMeter Test Extension, you must have urged to remediate the version of Apache JMeter installed on all the HCL OneTest Performance workbench and agent computers which HCL OneTest Performance uses through the JMETER_HOME environment variable.

What's new in 10.2.1

You can find information about the features introduced in this release of HCL OneTest Performance.

  • Support to add labels from the command-line interface

    You can now add labels by using a new parameter called -labels to test results when you run test assets from the command-line interface. See Running a test or schedule from a command line.

  • The execution agent is now renamed as the UI Test Agent

    The execution agent that was delivered along with HCL OneTest Performance Agent 10.2.0 is now renamed as the UI Test Agent.

  • Bug fixes

    Fixed customer-reported and internally found defects.

Installing the product

You can find information about the installation and upgrade instructions for HCL OneTest Performance.

For installation instructions, see Installation of HCL OneTest Performance.

Remember: You cannot upgrade the product to the latest version. You must uninstall the existing version of the product before you install the latest version of the product.

Known issues

You can find information about the known issues identified in this release of HCL OneTest Performance.

Table 1. Release documents - Fix list and known issues
Product Download document Knowledge Base

HCL OneTest Performance

Release document

Knowledge articles

The knowledge base is continually updated as problems are discovered and resolved. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

Contacting HCL support

You can find information about HCL technical support assistance for HCL OneTest Performance.

  • For technical assistance, contact HCL Customer Support.
  • Before you contact HCL support, you must gather the background information that you might need to describe your problem. When you describe a problem to the HCL support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
    • What software versions were you running when the problem occurred?
    • Do you have logs, traces, or messages that are related to the problem?
    • Can you reproduce the problem? If so, what steps do you take to reproduce it?
    • Is there a workaround for the problem? If so, be prepared to describe the workaround.