Release notes for HCL OneTest Server V10.1.0

Read about new features, system requirements, installation, known problems, and support for HCL OneTest Server.

Contents

Description

HCL OneTest Server is a server component 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

The following sections list the new features, enhancements or other changes made in this release.
  • Installation

    HCL OneTest Server can only be installed on the following platforms:
    • Red Hat OpenShift 4.2+

    • Ubuntu (using MicroK8s)

    For more information, see Installation of HCL OneTest Server.
  • Server Licensing

    You can purchase named user licenses for HCL OneTest Server and install the licenses on the FlexNet Operations server.

    For more information, see Licenses.

  • Backup and restore of user data

    You can back up and restore the user data in HCL OneTest Server V10.1.0. You can also migrate the backed-up user data from the previous versions of HCL OneTest Server to HCL OneTest Server V10.1.0.

    For more information, see Backing up and restoring the user data.

  • Test runs
    • Running AFT Suites on remote agents

      You can now select an agent added to your project on HCL OneTest Server to override the agent configured in the AFT XML file in the test asset.

    • Selecting test resources

      You can now select either the current or previous versions of the test resources that you want to run while you are configuring the test run.

    • Resetting test run configurations

      You can now reset the settings you configured for a test run when you are either initiating or repeating the test run. For more information, see Resetting the configuration settings for a test run.

    • Support for running an HTML test in a Compound Test on HCL OneTest Server

      You can now, run an HTML test as a compound test on HCL OneTest Server and choose to override the configured browser while configuring the test. For more information, see Configuring a run for Compound Tests that contains traditional HTML tests.

  • Test results
    • Navigating from a result to the associated Jaeger trace

      Now, test logs are delivered in a Jaeger format by default for executed compound tests and schedules. You can still set a Program Argument to re-enable the traditional test log format when you run the tests. For more information, see Test results and reports overview.

    • Relaunching an execution from the Results view

      From the Results view, you can re-execute a test with the same parameters as the ones that you previously set for the previous test run. You can also re-execute multiple tests at a time with the same parameters as the initial ones. For more information, see Re-executing tests from results.

    • Controlling Resource Monitoring sources

      Now you can use label matching to control what Resource Monitoring sources are collected during the execution of a Performance schedule. For more information, see Controlling Resource Monitoring sources in a schedule.

    • Functional Test reports

      A Unified Report is generated as a result of a functional test execution. For more information, see Test results and reports overview.

  • Resource monitoring
  • Projects
    • Selecting branches

      In earlier versions, branch selection was configured on the Repositories page and applied globally to all users. Now, each user is presented with a Branch field that lists all the branches of the repositories added to your project. The list is available in the Execution, Datasets and Overview pages HCL OneTest Server. For more information, see Test resource access by using the global branch.

    • Creating secret collections

      Members with the Tester role assigned in a project, can now create secrets collections. For more information, see Protecting API test assets by using secrets.

    • Project repository

      You can now add a repository with multiple folders to a single project. With this improvement, each project is now restricted to a single copy of a given repository.

  • Integrations
    • HCL OneTest Server integration with Azure DevOps

      You can now integrate HCL OneTest Server with Azure DevOps by using the HCL OneTest Studio extension to run tests as tasks in Azure DevOps pipelines. For more information, see Integration with Azure DevOps.

    • HCL OneTest Server integration with UrbanCode Deploy

      You can now integrate HCL OneTest Server with UrbanCode Deploy (UCD) by using the HCL OneTest Server UCD plugin to run tests on the UCD server. For more information, see Integration with UrbanCode Deploy.

  • Service virtualization
    • Running stubs

      You can now run stubs that you create in HCL OneTest API, from the Execution page on HCL OneTest Server. You can run IBM® WebSphere® MQ stubs and HTTP stubs on HCL OneTest Server. For more information, see Stubs: Starting or stopping.

    • Running stubs for Istio services
      After you create stubs for Istio in HCL OneTest API that virtualize services in a Kubernetes cluster, you can run those stubs on HCL OneTest Server. The stubs can virtualize services that use the Istio service mesh for the following types of requests:
      • Requests received by services in the Istio service mesh.
      • Requests sent from namespaces in the Istio service mesh to external services that are not in the Istio service mesh.
    • Stub usage statistics

      After you run stubs on HCL OneTest Server, you can view the stub usage statistics from the Stub Usage page. For more information, see Viewing stub usage statistics.

    • Routing rules

      You can view the details of the intercepts, proxies, or stubs with routing rules defined that are connected to HCL OneTest Server, from the Routing Rules page. For more information, see Viewing routing rules.

  • Test authoring
    • Using Excel Data Sources

      Excel Data Sources defined in HCL OneTest API projects can now be used as Datasets in your HCL OneTest Server projects. Note that Excel Data Sources that define a specific worksheet to use are ignored.

    • HCL OneTest Data

      HCL OneTest Data is a test data generation tool. You can use HCL OneTest Data to generate the sample test data to perform tests. This tool is now available as a component of HCL OneTest Server. For more information about the tool, see HCL OneTest Data overview.

    • Authoring datasets

      Now, you can create, edit, or delete a dataset in HCL OneTest Server. You can also publish the created dataset to Git repository so that other members of the project can use your dataset in their test asset run. For more information, see Datasets overview.

System requirements

For information about hardware and software compatibility, see the system requirements document.

Installing HCL OneTest Server

For instructions about installing the software, see Installation of HCL OneTest Server.

Note: You cannot upgrade to the latest version of HCL OneTest Server. You must uninstall the existing version and install the latest version of HCL OneTest Server.

Known problems

Table 1. Download documents and technotes
Product Download document Knowledge Base
HCL OneTest Server 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.

Contacting HCL support

HCL 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.