Release notes for HCL OneTest Server

This document includes information about What’s new, installation and upgrade instructions, known issues, and contact information of HCL Customer Support.

Contents

Product description

You can find the description of HCL OneTest Server.

HCL OneTest Server is a server that includes capabilities such as project and role-based security, Docker-based distribution and installation, and running of test cases. For more information about the server, see HCL OneTest Server overview.

What's new

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

The following sections list the new features, enhancements or other changes made in this release.
  • Support to export test results to a Jira Xray project

    When you use Atlassian Jira as a change management system on HCL OneTest Server and you use Xray as the test management application in Jira, you can now integrate Xray with HCL OneTest Server. With this integration, you can export the test results of the tests that run on HCL OneTest Server to an issue in your Jira Xray project. You can then view and use the test results in your project in Jira.

    See Integration with Xray test management for Jira.

  • Copying of the generated keys individually

    When you configured Atlassian Jira as a change management system on HCL OneTest Server, you were able to copy the public and consumer keys in a single action. However, it was difficult to differentiate the keys when you pasted them in the individual fields on the Jira server configuration page. You can now copy the public and consumer keys separately and use them to configure the Jira server.

  • Support to create defects on tests run by other project members

    Previously, you were able to create defects only on tests that you ran on HCL OneTest Server. You can now create defects in the change management system configured in your project on tests that are run by other project members too.

  • Enhanced publishing of association changes in the system model

    Previously, you were able to publish the changes made to the component associations with test resources in the system model from the Author > Changes page. You can now review and publish the association or dissociation changes of test resources with components in a system model from the System Model page. You can use the Image of the publish icon. icon on the System Model page to publish the association changes.

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

Removed capabilities

No capabilities were removed in this release.

Installing and upgrading

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

Installing HCL OneTest Server

For instructions about installing the software, see Installation of the server software.

Upgrading of HCL OneTest Server

For instructions about upgrading the software, see Server software upgrade methods.

Known issues

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

Table 1. Release documents - Fix list and known issues
Product Download document Knowledge Base
HCL OneTest Server Release document Knowledge articles

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.

Contacting HCL support

You can find information about 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.