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.
-
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.
-
Stopping stubs when the engine is stopped
You can now stop stubs that are running on an engine in HCL Quality Server when you stop the engine to prevent an autorestart of the stubs after the engine is stopped. See Viewing running agents.
-
Enhanced display of engine details
The display of the engine summary details is enhanced so that you can view the details of each engine that is running on HCL Quality Server from the Engines tab in the Infrastructure Dashboard without opening the engine cards. The Domain, Environment, Identifier, Process ID, and Number of stubs are displayed in sequence for each engine. However, you can find more details about the engine when you expand the engine cards. See Viewing running agents.
-
-
Technologies
-
Chai scripting in test actions
You can now use the Chai Assertion Styles of scripting in the Assert, Decision, and Function actions in tests. The Chai styles of assertions are the default scripting for these actions. With the introduction of the Chai scripting, the following features are changed:- You can select Chai as an option for scripting in actions where the legacy scripting and ECMA scripting are supported.
- You do not have to use the named variables in the response objects in Integration Tester actions.
- You do not have to explicitly tag or configure other actions to expose their data.
-
Timing-out the Run Command test step
When you configure the Run Command action in a test, you can now configure a Timeout, which is the period that is allowed for the commands to complete after which the command run is stopped. This option is enabled when the Wait for command execution to finish check box is selected. See The Run Command.
-
Using custom certificates designated as Certificate Authority
Previously, you could override the signing certificate that was deployed with Rational Integration HCL OneTest™ API HTTP/TCP proxy with any custom certificate. If the certificate was not designated as a Certificate Authority (CA) entity through the Basic Constraints certificate extension, you could start the HTTP/TCP proxy but client applications would usually abort the SSL connection. Also, the HTTP/TCP proxy did not display any error nor was the cause was identifiable.
Now, you must use a certificate that is designated as a CA entity through the Basic Constraint certificate extension. Also, the HTTP/TCP proxy shuts down and logs an error if you attempt to start the proxy with any certificate that is not designated as a Certificate Authority. See Modifying the configuration settings of the HTTP/TCP proxy and Starting and stopping the HTTP/TCP proxy.
-
Enhanced option in a File Subscribe action
Previously, you could browse and select the required text file and complete the File Name Pattern Override field in a publish-based action. For a subscribe-based action, you had to select the required text file by using the root directory. There was no option available to directly browse and select the required text file. As a result, it was difficult to select the correct path of the required text file.
Now, the Browse option is also enabled for a subscribe-based action. You can directly browse and select the required text file with any associated tags and complete the File Name Pattern Override field in a subscribe-based action. See File messages.
-
Enhanced Encryption and Signature algorithms fields
When you configure the outbound MIME messages to enable encryption or add digital signatures, you can now enter the Algorithm standard that you want to use instead of selecting it from the list. You can enter the name of the Algorithm in the fields, and a warning is displayed if the entered value does not match the name in the list. See Formatting a message with MIME, S/MIME, DIME, and multipart content.
-
Recording Istio traffic by using the service FQDN
You can now use the fully qualified domain name of a service in a Kubernetes cluster as the HTTP host when you record HTTP traffic in Istio. See Recording HTTP traffic in Istio.
-
Normalizing new line characters in SWIFT messages
When you either apply or edit messages that are based on the SWIFT schema, you can now opt to normalize the new line characters in the messages. When the new line characters are normalized, the CRLF characters are included in all lines in the messages. You can also set the preference to enable the normalization as a default setting. See Applying the SWIFT schema to a message.
-
Warning when performing a project refresh
Previously, when you used the menu option to refresh a project, HCL OneTest™ API discarded all your unsaved changes without any warning and refreshed the project in all open editors.
Now, HCL OneTest™ API alerts you by displaying a warning when you click , if there are unsaved changes in any of the open editors. You can opt to save all, part, or none of the changed work in open editors before refreshing the state of your project. See Refreshing a project.
-
Sending message body in a GET request
When you test an HTTP transport in HCL OneTest™ API by using the Publish action and you select the GET method, the message body is now sent as part of the request if one is specified.
-
JDK 11 support for the Java virtualization agent
The Java virtualization agent is enhanced to support use in applications that run on OpenJDK 11. See Java virtualization agent.
-
Removed the default port for the CentaSite server
The default port that was preset to connect to the Software AG CentraSite server in HCL OneTest™ API is now removed and you must enter the port that you configured for the CentraSite server to allow HCL OneTest™ API to connect.
-
-
Integrations
-
HCL OneTest™ API integration with HCL® Launch
You can now integrate HCL OneTest™ API with HCL® Launch by using the HCL® Launch plugin to run tests on the HCL® Launch server. See HCL OneTest and HCL Launch.
-
Deprecated capabilities
- No capability is deprecated.
Removed capabilities
- No capability is removed.
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 Installation of HCL OneTest API.
Installing HCL® Quality Server
For information about installation, see Installation of 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.
Upgrading HCL® Quality Server
If you use Installation Manager, you can find the upgrade requirements in HCL Quality Server upgrade information and requirements.
Known issues
You can find information about the known issues identified in this release of HCL OneTest™ API.
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.