Release notes for HCL OneTest API

This document contains information about What's new, installation, known issues, known limitations, and contact information of HCL support.

Contents

Product description

HCL OneTest API is an integration testing and virtualization tool that includes capabilities to automate and run tests earlier and more often to find problems sooner in the development cycle. See HCL OneTest API overview.

What's new

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

The following sections list the new features, enhancements, or other changes made in this release.
  • HCL OneTest Server

    For information about HCL OneTest Server, see Release notes.

  • HCL Quality Server
    • Tools page

      The list of agents changed for a release was updated. Review the Tools page of HCL Quality Server to see each tool and the version that it was last changed.

    • The latest version of the agents is displayed

      The IBM® WebSphere® MQ agent for IBM® z/OS® andIBM® CICS DPL agent now display the latest version when they are started. The latest MQ agent and CICS DPL agent have the same functions as the previous version of agents. Therefore, you need not upgrade them to the latest agent versions.

    • Scheduled tests are visible to all logged users on Rational Test Control Panel

      Previously, when you scheduled a test run that runs on HCL Quality Server, the domain-level security was not applied to the scheduled tests that resulted in the test being visible to all users logged on to HCL Quality Server.

      This continues to be the behavior as the domain-level security cannot be applied for scheduled test runs. However, when you schedule a test run in HCL OneTest API, the UI indicates that the scheduled test will be visible to all users logged on to HCL Quality Server.

    • Changing log levels of stubs without an auto restart

      Previously, when you changed the logging level of a stub that was running, the stub automatically restarted for the changes to take effect. At times, the auto restart of the stubs might have caused disruptions in your testing cycles.

      The behavior of the running stubs is enhanced, and now when you change the log levels of a running stub, the changes are applied without an auto restart of the stub.

    • Examples in Swagger UI

      Examples provided in the HCL Quality Server Swagger UI are for guidance only. You must use the response data received as input to subsequent calls. The Swagger API Documentation is updated for such usage in certain API calls.

  • Installing HCL OneTest API and other products in any of the supported languages

    You can now select any of the supported languages to install the product software and use the stand-alone installer in the selected language. The list displays the languages that you can select based on the display language that is configured on your computer.

    You can install HCL OneTest API, HCL OneTest API Agent, or HCL Quality Server in any of the supported languages including English. See Installing the product software by using the stand-alone installer.

    After you install the product software in the selected language, you can change the display language of the product, which can be different from the display language configured on your computer. See Changing the display language.

  • Technologies
    • Overriding results database

      When you want to run tests from the command line, you can now provide the URL, user name, password, and the database driver as arguments to override the Results Database that is configured in the project. You can optionally use an encrypted password that is generated by using the EncryptPassword application that is in the installation directory of HCL OneTest API.

    • Viewing progress of results deletion

      Previously, when you used the command line to delete results in a results database, you were not able to ascertain the progress nor the number of records that were being deleted.

      Now, you can view the progress of results deletion in a progress bar when you use the delete all results command. When you use the delete all results keeping <argument> command, you can view the number of records being deleted along with the progress in a progress bar.

      See Deleting all results by using the command line.

    • Recording SAP Hana S4 IDocs

      You can now record SAP Hana S/4 IDocs by using the HCL OneTest API ABAP plugin.

    • Support for IPIC and DPL

      HCL OneTest API now supports IPIC and DPL with CICS Transaction Server 5.6.

    • Support for producer-driven Contract testing

      Previously, you were able to create and run consumer-driven Contract tests in HCL OneTest API.

      Now, you can use HCL OneTest API to create and run producer-driven Contract tests by creating stubs that subscribe to the messages sent by the consumer. Setting the stub property to validate the contract, ensures that the schema defined for outgoing messages from consumers are validated by the schema defined for the expected messages received by the stub. Also, if the validation fails, a response is sent to the consumer about the validation errors.

      HCL OneTest API also supports the creation of Contract tests and stubs when you synchronize resources to perform Contract testing.

      See Contract testing.

    • Support for symmetric and asymmetric key-based signature algorithms in SOAP requests

      You can now use any of the supported HMAC symmetric or asymmetric signature algorithms to sign certificates that you want to use in SOAP requests.

      The supported symmetric signature algorithms are as follows:
      • HMAC-MD5
      • HMAC-SHA1
      • HMAC-SHA256
      • HMAC-SHA384
      • HMAC-SHA512
      The supported asymmetric signature algorithms are as follows:
      • DSA-SHA1
      • ECDSA-SHA1
      • ECDSA-SHA256
      • ECDSA-SHA384
      • ECDSA-SHA512
      • RSA-SHA1
      • RSA-SHA256
      • SHA1
      • SHA384

      See Adding signatures.

    • Adding multiple child nodes to the query or mutation GraphQL document node

      Previously, you were able to add only one query or mutation node as a child to a GraphQL query or mutation document node.

      Now, you can add multiple query or mutation nodes as children to a GraphQL query or mutation document node.

      See Applying the GraphQL schema to a message and Editing GraphQL messages.

    • Working with DFDL-based messages is improved

      Previously, when you worked with messages that were based on a DFDL schema, empty fields prevented the message from being collapsed.

      Now, HCL OneTest API is enhanced to correctly manage the DFDL based messages as follows:
      • Newly created fields are populated with either the default or ibmDfdlExtn:sampleValue attributes.
      • Default values are added for boolean, byte, or numeric values if the values are not specified when the content in messages is previewed or sent.

      See Creating a DFDL schema.

    • Sending an error response by stubs

      When you use the Message Case in a Message Switch action to receive messages in a stub, you can now select the Send Error Response option to force the stub to send a response if the incoming message fails the validation that is set. The validation points are set in the Assert tab of the Message Case action configured in the stub.

      See The Properties tab.

    • Support for MQ 9.2

      The HCL OneTest API API agent for MQ (z/OS) now supports MQ 9.2.

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 are deprecated in this release.

Removed capabilities

Support for the following operating systems or supported software that were announced in previous releases as deprecated are removed in this release:
  • No capabilities are removed in this release.

Installing and upgrading

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

Installing HCL OneTest API

For information about installation, see Installing HCL OneTest API.

Installing HCL® Quality Server

For information about installation, see Installing HCL Quality Server.

Upgrading HCL OneTest API

If you use Installation Manager, you can find the upgrade requirements in HCL OneTest API upgrade information and requirements.

If you use the stand-alone installer to install the software packages, you cannot upgrade the product software. You must uninstall the previous version of the product software and install the latest version by using the stand-alone installer.

Upgrading HCL® Quality Server

If you use Installation Manager, you can find the upgrade requirements in HCL Quality Server upgrade information and requirements.

If you use the stand-alone installer to install the software packages, you cannot upgrade the product software. You must uninstall the previous version of the product software and install the latest version by using the stand-alone installer.

Known issues

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

Table 1. Release documents - Fix list and known issues
Product Download document Knowledge base
HCL OneTest API Release document HCL support

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.

The only known limitation is that the Logical View does not display a diagram. Instead, a tree view, similar to that used in the Test Factory and Test Lab is used to support the logical components of the SUT.

Contacting HCL support

  • 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.