Release notes

This document contains information about new features and enhancements for HCL OneTest Embedded and links to useful information about the products.



HCL OneTest Embedded is a complete test and runtime analysis tool set for systems development created in any cross-development environment.

HCL OneTest Embedded provides tools for automated component testing, code coverage, memory leak detection, performance profiling, and UML sequence diagram tracing.

What's new in HCL OneTest Embedded 8.3.1

The following sections list the new features, enhancements or other changes made in this release:
  • Monitoring
    • This feature targets cyclic-executive applications, that is applications that mainly rely on a cycle where input data are read and output data are set at each cycle. These input/output data are implemented with global variables.

      See Application monitoring

    • The complete application is instrumented to be able to access to the global variables in read/write mode with various means (socket, files…). See Prerequisites to monitoring applications.
    • A new view in HCL OneTest Embedded for Eclipse IDE is available to interactively modify the input data and display the output data. See Monitoring a cyclic executive application.
    • Output data can be displayed as curves on a graphical view.
  • Test Case Generation for C (preview):
    • This is a preview feature of the new test case generation integrated in HCL OneTest Embedded for Eclipse IDE only for now.
    • When this feature is enabled, the source code is analyzed and the test cases can be generated from:
      • The call graph: A coverage objective can be provided to generate test cases.
      • The coverage viewer: Clicking on a branch displays in a new view the precondition to satisfy in input of the function under test, and a new test case can be generated to satisfy this precondition.
    Note: No customer support is ensured for this feature for now. If you have any queries or issues about the Test Case Generation for C (preview) feature, you can request help from OneTest Embedded forum.
  • MISRA updater:
    • When you update from an old version of HCL OneTest Embedded and you use MISRA in HCL OneTest Embedded for Eclipse IDE 8.3.1 for the first time, you are requested to update the configuration rule with the new rules added to the new version. By default, the unselected rules are disabled, they must be selected to be enabled. See Configuring code review rules.
    • In HCL OneTest Embedded Studio, the configuration file is automatically updated and the new rules are disabled. See Running a code review.
  • Support for Eclipse 2020-06 (4.12)

    HCL OneTest Embedded is still delivered with Eclipse 4.7.2 but it can be also installed on Eclipse 2020-06 (4.12).

  • TDP Visual 2019

    A new Target Deployment Port dedicated to Microsoft Visual 2019 is delivered.

System requirements

For information about hardware and software compatibility, see System Requirements.

Installing the product

You cannot upgrade HCL OneTest Embedded from an earlier version of the product to HCL OneTest Embedded 8.3.1. If you have an earlier version of the product, you must uninstall it before installing HCL OneTest Embedded 8.3.1.

To install the product, see the Installing section in the navigation. You will find additional information in the release note that is delivered with the product.

Fixed and known issues

In the release documentation that is delivered with the product, you will find the lists of fixed and know issues.

Product Download document Knowledge Base
HCL OneTest Embedded HCL OneTest Embedded 8.3.1 release document HCL support

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.