Known issues
You can find the known issues that are identified, if any, in this version of HCL DevOps Test Embedded (Test Embedded). You can also find the known issues identified in the earlier versions of Test Embedded. 2023.12 (9.0.0)
Known issues in Test Embedded 2023.12 (9.0.0)
The known issues identified in Test Embedded 2023.12 (9.0.0) are as follows:
|
ID |
Description |
|---|---|
|
TESTRT-3592 |
In a PTU file, when you try to initialize or check the results of an array of structures and the structures that contain arrays, might lead to an index error. This error leads to an incorrect initialization or comparison, and results in a test failure. To work around this problem, instead of having a single test instruction for the entire structure or array, write one test instruction per field. |
|
TESTRT-3808 |
In DevOps Test Embedded Studio Project Explorer, a parent node incorrectly displays a success status even when one or more of its child nodes fails.
|
Known issues from earlier versions
The known issues identified in the earlier versions of Test Embedded that are still applicable are as follows:
|
ID |
Description |
Identified in version |
|---|---|---|
|
TESTRT-1436 |
In Eclipse, in the Test Case editor, the red cross on Stub Behavior is not refreshed after execution. Workaround: Select another result to display, then re-select the original one. |
8.3.0 |
|
TESTRT-1303 |
The Studio C++ wizard does not generate stub and OTD properly when the method to stub is declared into a class which is part of a template.Workaround: Change the .stb and .otd manually once generated by the wizard. |
8.3.0 |
|
TESTRT-1368 |
The TDP cvisual10 and cvisual10_64 do not detect FIU properly due to removed system methods. Workaround: Set Library/Heap Management Configuration/FIU detection to RTRT_NONE. |
8.3.0 |
|
TESTRT-2080 |
Control Coupling and Worst Stack reports are not available on Test Suite results. |
8.3.0 |
|
TESTRT-2466 |
On large trace file, there is no way to stop the loading. |
8.3.0 |
|
TESTRT-3472 |
In recent gcc compiler (cygwin), the qualification kit could not compile after instrumentation that uses absolute paths. |
8.3.2 |
|
TESTRT-2132 |
Depending on the compiler definition, plain char may be signed or unsigned. So, any rule related to unsigned the type should be ignored when underlying type is a plain char. |
8.3.0 |
|
TESTRT-3234 |
In Misra 2004, the rule M6.1.1 is not triggered on plain char when char are unsigned by default. |
8.3.2 |
|
TESTRT-3472 |
In recent gcc compiler (cygwin), the qualification kit could not compile after instrumentation that use absolute paths. |
8.3.2 |
|
TESTRT-2825 |
Testing a C file that requires header (.h) files, when linking these files, we lost the visibility of the data types (required for enumerated types and stubs that return an enumerated type). What would happen if, when |
8.3.1 |
|
TESTRT-1897 |
Tiny toolbar icons for Coverage and Performance reports |
8.3.1 |
|
TESTRT-2275 |
In chapter 10, 'essential type' is calculated for all expression nodes. Enums have a specific behavior as they can be seen either as true enum, or as signed (in case of anonymous enums). Result may be erroneous on enum constants. |
8.3.0 |
|
TESTRT-1915 |
On RedHat 7, the Call Graph is not displayed properly, which makes it nearly unusable. |
8.3.0 |
|
TESTRT-2610 |
On very large test reports, rod2xrd could crash (depending of the machine memory size).Workaround: Reduce the size of the test report by running the test case selecting a subset of test cases. |
8.3.0 |