Release notes for HCL OneTest™ API

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.

Previously, IBM® Installation Manager allowed you to rollback HCL® Quality Server. The rolled back version was unable to be started because the workspace was from a later version. Rolling back HCL® Quality Server is now not supported by Installation Manager.

See Installation considerations for HCL Quality Server.

The version of H2 database that HCL® Quality Server used for storing Virtual Service, Scheduling and optionally metrics data was updated.

When you install or upgrade HCL® Quality Server against an existing workspace, you can expect a longer duration for the operation and are informed about the migration of existing resources to the new database format. The location of the migrated resources is also indicated by the installer.

See Installation considerations for HCL Quality Server.

Support is now enabled for Camel 3.x transports that replaces the previously supported Camel 2.x transports. You can now test the technologies that are supported by Camel versions up to and including 3.14.x.

See Prerequisites for testing the technology endpoints supported by Camel.

The default isolation level for messages that are read by a Kafka consumer in HCL OneTest™ API is set to read committed messages. If you want to change the default level so that the consumer reads the uncommitted messages, you must set the -Dgreenhat.kafka.consumer.extra property as a JVM argument in either the Library Config file or the IntegrationTester.ini file.

Previously, when you used Active Directory as the Authorization Realm for a project, you were able to create an unsecured connection.

You can now create a secured connection with Active Directory by using the SSL option. You can opt to trust a specific certificate, or all the certificates that are presented by the Active Directory Domain Controller.

See Project settings.

Previously, you were able to create test data by using tags in tests as an Excel spreadsheet. You can now create test data from tests as a CSV file.

See Creating test data from tags in a test.

REST APIs are added that enable you to work with scheduled tests on operations such as list the scheduled tests, run scheduled tests, modify or delete a scheduled test. For details see the Swagger documentation accessible from the HCL® Quality Server URL.

When you open a project that has a results database configured, and the results database is unavailable, a stack trace is no longer displayed in the log.

Previously, the output of test actions, including those from scheduled tests, were included in both results and the application log files making reading of the agent logs tedious.

HCL OneTest™ API Agent is enhanced to separate the logging for test actions and the logs are now only to be found in the results and the engine logs.

Previously, when you built the actions for the query results in the Store or Assert tab of the SQL Query action definition dialog box, the column names were restricted to a fixed column width. Now, HCL OneTest™ API is enhanced to adjust the column width to match the characters in the column name, which lets you view the complete column name.

When you use the HCL OneTest™ API Azure extension in Azure pipelines to run tests on HCL OneTest™ API, you can view the test results on the Jobs page.

If you want to view the results of the test runs on the test plans dashboard, you must set up test plans with test cases for your project in Azure. You must also provide details about the Azure server, your personal access token, the Azure project, the test case, and the test plan while you configure the test run for the test results to display on the test plans dashboard.

See Running tests in an Azure DevOps pipeline.