Release Notes
This document contains information about new features and enhancements for HCL OneTest™ Embedded and links to useful information about the products.
Contents
Description
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.2
You can find information about the features introduced in this release of HCL OneTest™ Embedded.
- Integration with ETM 7.0.2
- Better support of C++20 syntaxes
-
Miscellaneous:
- TDP for Visual Studio 2022
- Export HTML reports in HCL OneTest™ Embedded for Eclipse IDE
Installing the product
You can find information about the installation and upgrade instructions for HCL OneTest™ Embedded.
For instructions about installing the software, see Installing.
You cannot upgrade HCL OneTest™ Embedded from an earlier version of the product to version 8.3.2. If you have an earlier version of the product, you must uninstall it before installing HCL OneTest™ Embedded 8.3.2.
Known issues
Product | Download document | Knowledge Base |
---|---|---|
HCL OneTest™ Embedded | 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
- 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.