Defect fixes

TP-89626

Previously, the terminated Execution pods incorrectly displayed the status as an error when the API test or API Suite returned the result as Fail.

This problem is fixed.

TP-88262

Previously, when you ran Web UI tests that had a large number of test steps, the unified report failed to be exported as a PDF.

This problem is fixed.

TP-89553

Previously, the unified report was displayed incorrectly when you ran a Compound Test that contained mobile tests, which ran on either the devices, emulators, or simulators that were connected to an agent computer or the devices that were connected to a mobile device cloud.

This problem is fixed.

TP-89167

Previously, when you exported a statistic report for a test result, the downloaded report displayed the Agent Health report as the default report.

This problem is fixed.

The downloaded report now displays the UI Statistical report as the default report.

TP-86087

Previously, when you started a large number of test assets simultaneously, you were required to determine the capacity of the system, size of projects, and adjust the rate accordingly.

This problem is fixed.

TP-88119

Previously, if you set the Helm option gateway.allowOrigin during installation of HCL OneTest™ Server, it was mandatory for you to include the server URL in the string.

This problem is fixed.

Now, you need to only include strings for additional servers and you do not have to include the server URL string in the gateway.allowOrigin option.

TP-88111

Previously, the default configuration in Keycloak incorrectly assigned all users of HCL OneTest™ Server the privileges of a server administrator.

This problem is fixed.

TP-88079

Previously, when members of a team space entered the URL of a page in a project, they were incorrectly provided the access to view the page even though they were not a member of that project.

This problem is fixed.

TP-86646

Previously, when filtering the virtual service instances that are listed on the Instances page by activity, HCL OneTest™ Server incorrectly filtered by overall activity rather than recent activity.

This problem is fixed.

TP-86105

Previously, the project overview page did not display the statistics of the test results that were published to HCL OneTest™ Server from any of the desktop products.

This problem is fixed.

Now, if a project has no configured repositories, the project overview page displays the statistics of the test results published to HCL OneTest™ Server from any of the desktop products.

TP-84738

TP-84688

TP-84675

TP-84492

TP-84022

Previously, when you ran a Web UI test with an associated dataset, the test failed to read all the rows and stopped after completing a few iterations.

This problem is fixed.

TP-83686

A Sign-Up link is no longer offered on the login page by default to improve security posture. It can be enable during install or afterward from Keycloak by enabling Login > User Registration.

TP-82448

Previously, when you ran a performance test that contained integration tests on HCL OneTest™ Server, the hierarchy of test iteration in the test log was incorrect. Therefore, the integration test steps in the test log were displayed under the first activity that was captured for the performance test.

This problem is fixed.

TP-76020

Previously in Keycloak, when using the LDAP user provided certificates were not imported into the Keycloak truststore that resulted in errors when authenticating.

This problem is fixed.

TP-81758

Previously, if you specified a secrets collection while configuring a run of a virtual service, the specified collection was ignored and an attempt was made to use a secrets collection with the same name as the environment.

This problem is fixed.

TP-81035

Previously, the default configuration of HCL OneTest™ Server had access to requests from any domain. Therefore, HCL OneTest™ Server was exposed to cross-origin resource sharing (CORS) attacks.

This problem is fixed.

TP-81017

Previously, if you attempted to edit an API Suite that was in the git branch of your server project, the containerized API editing session was not launched because of non-omitted spaces in the path of the asset.

This problem is fixed.

TP-80637

Previously, while you installed HCL OneTest™ Server on Azure Kubernetes Service (AKS) if the postgresql-init job did not complete early, it might have remained in a Pending state due to insufficient CPU resources.

This problem is fixed.

TP-80565

Previously, when you deployed HCL OneTest™ Server on Azure Kubernetes Service (AKS), and if you did not set up the Domain Name Server (DNS) resolution of the client, you were unable to open a new editor session.

This problem is fixed.

TP-80321

Previously, when you ran a performance or functional integration test on HCL OneTest™ Server that had the API test type as a RAML definition, the test failed to run.

This problem is fixed.

TP-79765

Previously, if two instances of a virtual service resource were run simultaneously with different environments and later stopped, the virtual services displayed their status as STOPPED but the virtual services might be left running in the container.

This problem is fixed.

TP-79322

Previously, when a virtual service on the server was running and the server execution service restarted, it resulted in the loss of the routing rules for the virtual service.

This problem is fixed.

TP-79272

Previously, when you started an HTTP virtual service by using the REST API and supplied an environment name where the name differed from the desktop project value in its letter-casing, for example, env compared to Env, the virtual service might have started but the routing rules were not created.

This problem is fixed.

TP-79218

Previously, if you attempted to use the dataset override when you started an instance of a virtual services resource, you might have noticed that the dataset override did not take place.

This problem is fixed.

TP-79185

When you run two virtual services concurrently from HCL OneTest™ Server, where the virtual services come from the same desktop project but are run with different environments, traffic might fail to be routed to one of the virtual service and HTTP 502 errors might be encountered.

This problem is fixed.

TP-78842

Previously, when you ran a test on a remote Kubernetes cluster from a HCL OneTest™ Server installation that was configured with a non-default ingress secret name, the remote execution pod failed to start.

This problem is fixed.

TP-78841

Previously, when you scheduled a test to run on a remote agent associated with your project in your team space, the test run failed to run and an error message was displayed.

This problem is fixed.

TP-78219

Previously, when you updated the name of the project in Jira, and if you have used that project name on HCL OneTest™ Server, you were unable to configure the updated project name in the CHANGE MANAGEMENT SYSTEM tab of HCL OneTest™ Server.

This problem is fixed.

TP-78109

Previously, when you stopped a large number of virtual service instances, you might have seen a 504 error although the virtual service instances were stopped successfully.

This problem is fixed.

TP-77049

Previously, when you ran the reconcile-secrets.sh script to update the password seed, the script displayed an error message.

This problem is fixed.

TP-76098

Previously, during the deployment of HCL OneTest™ Server V10.2.0 on Azure Kubernetes Service (AKS) V1.20 or later, the deployment was failing with an error message.

This problem is fixed.

TP-74534

Previously, when you tried to publish a created dataset after the migration from an earlier version to 10.1.3 or 10.2.0, you were unable to publish the dataset to a Git repository.

This problem is fixed.

TP-73109

Previously the command-line interface was displaying warnings about Ingress deprecation during the installation of HCL OneTest™ Server 10.1.3 or 10.2.0 on Lightweight Kubernetes (k3s).

This problem is fixed.

TP-71950

Previously, when the server was under high load, in some cases, the results microservice restarted indefinitely. This issue occurred when the Kubernetes supervisor stopped the results microservice during a database locking process.

This problem is fixed.

TP-71416

Previously, when you attempted to run an API Suite on HCL OneTest™ Server that is installed on OpenShift, and when the API project contains a vast set of resources, the Execute button in the Execute test asset dialog box was enabled after a delay or at times not enabled at all.

This problem is fixed.

TP-70940

Previously, during the installation of HCL OneTest™ Server, checks were not made to verify that the supplied ingress domain was valid.

This problem is fixed.

TP-72278

Previously, when you attempted to run an API Suite on HCL OneTest™ Server that is installed on OpenShift, and when the API project contained a vast set of resources, the Execute button in the Execute test asset dialog box was enabled after a delay.

This problem is fixed.

TP-58061

Previously, when you shut down HCL OneTest™ Server, the Suites, Compound Tests, or Schedules that were running did not stop.

This problem is fixed.

TP-70414

Previously, when you installed HCL OneTest™ Server V10.1.1 on an OpenShift platform where OpenShift Container Storage (OCS) was not available (For example, the IBM Cloud) then test asset runs failed.

This problem is fixed.

TP-69452

Previously, when you started stubs on HCL OneTest™ Server, occasionally the stubs remained in transition and did not run.

This problem is fixed.

TP-67330

In HCL OneTest™ Server V10.1.2, Kafka is replaced with RabbitMQ.

Now you do not see a restart of the Kafka pod and some of the other microservices when the server is in an idle state.

TP-67306

Previously, from the Execution tab, you could not use the keyboard to search and select a branch.

This problem is fixed.

TP-66731

Previously, you might have experienced errors when you published large reports, either from desktop products or when you executed a test on the server.

This problem is fixed.

You no longer have to set the options recommended as a workaround to publish large reports.

TP-62379

If you (as a user) requested to join an orphaned project, you saw a 404 not found error. You now see the following message: You can't request to join a project that has no owners.

TP-56453

After about 20 minutes of an inactive browser session for HCL OneTest™ Server, if you attempted to use the existing browser session, you had to authenticate again by providing your username and password.

This problem is fixed.

TP-68740

This version addresses a problem with datapool encrypted values being logged as clear text to Jaeger log.

TP-67208

Previously, when you used the Undo or Redo options for a change in a dataset by using the CSV editor, the Save or Discard options were grayed out, thus you could not save or discard the changes.

This problem is fixed.

TP-67032

Previously, before you upgraded to a new version, you had to cancel any scheduled execution.

This problem is fixed.

TP-60737

Previously, GIT repositories that contained projects at the root level and were not under a subdirectory were not supported and did not work with HCL OneTest™ Server.

This problem is fixed.

TP-66237

Previously, HCL OneTest™ Server projects were sorted by date.

Now, server projects are sorted alphabetically.

TP-63775

Previously, in HCL OneTest™ Server, it was not clear that classifications could only be made for encrypted datasets.

This problem is fixed.

TP-63156

Previously, Docker images that were created with no tag were assigned the latest tag. As the docker ps command did not show the latest tag anymore since the Docker 19.03.05 release, the Docker images were not detected and were not correctly monitored.

This problem is fixed.

TP-63149

Previously, intermediate <none>:<none> Docker images were represented as is and could not be selected individually in Resource Monitoring counters.

This problem is fixed.

TP-62643

If you backed up a project with both API suites and stubs on HCL OneTest™ Server 10.0.0, when you restored that backup on HCL OneTest™ Server 10.0.2, the stubs were missing.

This problem is fixed.

TP-62571

If you wanted to add multiple repositories to a project in HCL OneTest™ Server you could not add another repository until the last repository completed its synchronization.

This problem is fixed.

TP-62417

Previously, a user who was no longer a member of a project might be displayed in the Secrets tab. If a user was removed from a project and then added back to that project, the user would have the same access to secrets as they had before being removed.

This problem is fixed.

TP-62338

Previously, an IBM WebSphere MQ stub that was configured to use more than one transport did not appear on the Execution page of the HCL OneTest™ Server.

This problem is fixed.

TP-61897

Previously, if you restored a backup, it failed due to existing execution containers.

This problem is fixed.

TP-61786

Previously, when you entered a URL for a test result directly into a browser or you clicked a link to a test result in the Jenkins console output from the Jenkins HCL OneTest™ Server plugin, and you were not logged in to HCL OneTest™ Server, you saw the following message: Request cannot be processed: Unauthorized page.

This problem is fixed.

TP-61179

Previously, executing a test on a non-English system failed.

This problem is fixed.

TP-61153

Previously, the project search field was case-sensitive. For example, if your project was named MYPROJECT and you searched for myproject, HCL OneTest™ Server did not show any results.

This problem is fixed.

TP-58125

Previously, HCL OneTest™ Server did not release system resources after they had exited.

This problem is fixed.

TP-57543

Previously, if the server hostname was changed, it was necessary to run ./prepare.sh and log in to the Keycloak Admin Console to change the testserver client URLs. Otherwise the message Invalid parameter: redirect_uri was displayed on the Login page.

This problem is fixed.