Release notes for HCL OneTest API and HCL OneTest Virtualization V10.1.0

Read about new features, system requirements, installation, known issues, known limitations, and support for HCL OneTest API and HCL OneTest Virtualization

Contents

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. For more information, see HCL OneTest API overview.

What’s new

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.

    • Stubs list on the Infrastructure dashboard

      Now, stubs listed on the Infrastructure dashboard of HCL Quality Server are sorted in alphabetical order.

  • Mainframe
    • IBM WebSphere MQ exit

      The IBM® WebSphere® MQ exit for z/OS and the IBM CICS DPL exit now display the latest version when starting. These newer exits function the same as the previous exit, and there is no need to upgrade to the newer exits.

    • MQ transports

      MQ transports can now be configured to specify the model queue used when issuing MQ programmable command format (PCF) commands. For more information, see MQ Transport: Advanced settings.

    • Support for IBM® App Connect Enterprise V11.0

      HCL OneTest API is enabled to support the synchronization of resources that are created on the Integration Node of IBM® App Connect Enterprise V11.0 formerly known as IBM® Integration Bus in its released versions: V9.0 and V10.0. Each supported node that exposes a service endpoint or that consumes another service endpoint is mapped to an operation in the logical model of your HCL OneTest API project. You can create tests and stubs for the Integration Node resources and run them in HCL OneTest API. You can now configure the secured communications between the Integration Node and HCL OneTest API when you create the connection to the Integration Node in IBM ACE (V11.0) or IIB (V10.0). For more information, see Testing with IBM Integration Bus.

    • Enhanced filtering capabilities for IMS Connect transactions

      The IMS Connect stubbing and routing rules are enhanced in their filtering capabilities to include the values specified for Message-Type, Client ID, Datastore, and Transaction Code settings. Therefore, a more fine-grained selection of events is now possible in the stubbing and routing rules. This enhancement might affect the existing stubs and operations when deployed in V10.1.0 to capture fewer messages than in the previous versions.

      When recording or stubbing with IMS, the Network page in HCL Quality Server displays the Message-Type, Datastore, Client ID, and Transaction Code in the Target field that enables you to locate specific monitors and rules.

    • Support for IBM® WebSphere® MQ

      Support for IBM® WebSphere® MQ V7.x is deprecated. Support now includes V8.x through V9.x.

  • Technologies
    • Selecting the pattern for topics to record traffic in Kafka

      The selection of multiple topics to record from the Recording Studio tab for a logical Kafka Connection is changed. You can now enter each topic on a separate line, use wildcards, or patterns to specify the topics to record. For more information, see Recording Kafka transport traffic.

    • Recording Istio traffic

      It is now possible to record the HTTP traffic within an Istio service mesh in a Kubernetes cluster. HTTP requests between the services in the service mesh and HTTP requests received and sent from the Istio service mesh can be recorded from HCL OneTest API. For more information, see Recording HTTP traffic in Istio.

    • Database drivers

      Database drivers that you added to the Library Manager are now displayed while configuring a database connection. For more information, see Configuring the physical database resource.

    • RQM Agent as a Windows service

      Now, if you have installed only HCL OneTest API, you can configure the RQM Agent as a Windows service. For more information, see Configuring the RQM Agent as a Windows service.

    • HTTPS proxy port 3129 is deprecated

      Earlier, you could send the HTTPS traffic to the HTTP/TCP proxy server by using the port 3129 and the HTTP traffic by using the port 3128. The port 3129 is now deprecated. The port 3128 that earlier allowed both the HTTP and HTTPS traffic is retained as the only port for both the HTTP and HTTPS traffic. The https-proxy element in the registration.xml that was used for the HTTPS and SSL-based forwarding rules for transports such as TCP, IMS, IPIC, MQTT, or KAFKA, is now renamed to ssl-settings.

      The addNumbers example that is packaged with HCL OneTest API is now configured to use port 3128 for both HTTP and HTTPS traffic.

    • Enhanced messaging actions for the Email transport

      You can now create tests that use the Request/Reply action when testing with the email transport. You can also configure the SMTP and IMAP mail servers for the email resources. The email transport is enhanced to support secure communications between HCL OneTest API and the mail servers. For more information, see Testing with the email transport.

    • Support for testing with Apache Camel components

      You can now test the technologies that are supported by Camel V2.24.3 in HCL OneTest API. You must add the JAR files for the Camel component and dependent libraries to Library Manager so that HCL OneTest API can access that technology. You can then configure the endpoints provided by the Camel component that are in your test environment as a physical resource in the HCL OneTest API project. You can create tests and stubs to test and virtualize the services provided by the Camel component in HCL OneTest API. For more information, see Testing with Apache Camel components.

    • HIT suffix for RabbitMQ

      From version V10.1.0, a new suffix HIT is used when creating a RabbitMQ or a Software AG Universal Messaging transport. For all assets created before V10.1.0, you can manually change the RIT suffix for the HIT suffix in the Transport recording settings and create a HIT Queue, Channel or Data Group accordingly.

    • IATA formatter

      The IATA formatter was deprecated and no longer appears when you create messaging actions. Existing formatters remain.

  • Integrations
    • HCL OneTest API integration with Azure DevOps

      You can now integrate HCL OneTest API with Azure DevOps by using the HCL OneTest Studio extension to run tests as tasks in Azure DevOps pipelines. See Integration with Azure DevOps.

System requirements

For information about hardware and software compatability for HCL OneTest API, see the system requirements document.

For information about hardware and software compatability for HCL OneTest Virtualization, see the system requirements document.

Installing HCL OneTest API and HCL Quality Server

For information about installation, see:

Installing HCL OneTest Virtualization

For information about installation, see Installing HCL OneTest Virtualization.

Known problems

Table 1. Download documents and technotes
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.

Known limitations

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

HCL Customer Support provides you with technical assistance.

Before you contact HCL support, gather the background information that you will need to describe your problem. When describing a problem to an 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.