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 you play back the test. See HCL OneTest Performance overview.

What's new

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

  • Support to control test runs for error handling

    A new error condition Test Verdict Failed is added to Error handling to manage the test when the overall verdict of the test is failed. The error condition can control the behavior of the test and can contribute to the health of the test. See Error conditions.

  • Support to delete any row or all rows in datasets

    You can now use new two methods to delete rows in a dataset. When you use IDatasetController in a custom code, you can use the following two methods to delete rows:

    IDatasetController.deleteRows(fromIndex, toIndex) - You can use this method to specify a range of rows to delete. The index starts at 1.

    IDatasetController.deleteAllRows() - You can use this method to delete all the rows in the dataset.

    See Deleting rows in a dataset.

  • Customizing names of exported statistical reports

    You can now specify a pattern that defines the file names of the exported statistical reports when you run tests from the command line. See Command-line parameters.

  • Support for Revenera 2022.12

    With Revenera 2018.02 (LLS 1.0) reaching EOS, you can now use Revenera 2022.12 (LLS 3.0) as a local license server to host licenses for HCL OneTest Performance.

Deprecated capabilities

You can find information about the capabilities that are deprecated in this release and are planned for a removal in a future release.

Note: You can contact the HCL Client Support team if you have any concerns.
  • No capabilities were deprecated in this release.

Removed capabilities

No capabilities were removed in this release.

Installing the product

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

Installing HCL OneTest Performance

For installation instructions, see Installation of the product by using the stand-alone installer.

Upgrading

You cannot upgrade HCL OneTest Performance to the latest version. You must uninstall the existing version of HCL OneTest Performance before you install the latest version.

For installation instructions, see Installation of the product by using the stand-alone installer.

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.