This document contains the LabVIEW 2020 Unit Test Framework Toolkit known issues that were discovered before and since the release of LabVIEW 2020 Unit Test Framework Toolkit <version>. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 166658 | 635510 |
Adding a diagram disable structure to a VI can cause the reported code coverage to be 100%Workaround: There is currently no known workaround for this issue. |
Reported Version: Unit Test Framework 2015 SP1 Resolved Version: N/A Added: Jan 22, 2018 |
| 755937 | 171553 |
File load conflict after dragging multiple LV Classes to another contextWorkaround: Rename the lvtest files to different names. Or remove those lvtest files from the project and re-add them. |
Reported Version: Unit Test Framework 2009 Resolved Version: N/A Added: Aug 4, 2009 |
| 882161 | 555738 |
In certain cases, Unit Test Framework cannot detect a LV Class object inside a Packed Project Library when block diagrams are removed.Workaround: Set the block diagram of the VI calling the LV Class to not be removed in the Packed Project Library's build specification. |
Reported Version: Unit Test Framework 2014 Resolved Version: N/A Added: Mar 8, 2016 |
| 792286 | 471993 |
Cannot create Unit Test for VI with control connected to the terminal and inside a tab controlWorkaround: If possible, do not have a control connected to the VI's terminal and inside a tab control. |
Reported Version: Unit Test Framework 2010 Resolved Version: N/A Added: Feb 11, 2020 |
| 792415 | 420795 |
When creating a custom LV project template with the Unit Test Framework .lvtest file, the new project will overwrite the original template when saving instead of creating a new instance with new files.Workaround: There is currently no known workaround for this issue. |
Reported Version: Unit Test Framework 2012 Resolved Version: N/A Added: Feb 11, 2020 |
| 792325 | 475037 |
Enabling loop iteration parallelism in For Loops results lower code coverage than expectedA For Loop configured for parallelism is incorrectly counted as an uncovered diagram when calculating code coverage Workaround: Turn off parallelism or set the for loop to "Allow debugging" for the code coverage test |
Reported Version: Unit Test Framework 2011 SP1 Resolved Version: N/A Added: Feb 11, 2020 |
| 225408 |
Unit Test Framework .lvtest file opens blank and reports that a class cannot be loaded if there is an unrelated class that is broken in a project.Unit Test Framework .lvtest file opens blank and reports "LabVIEW: (Hex 0x55D) Class could not be loaded". This occurs if the project has an unrelated class that cannot be loaded. If the unrelated class is loaded, the .lvtest file loads successfully and works as expected.
Workaround: Make sure all unrelated classes are loaded or removed.
|
Reported Version: Unit Test Framework 2018 Resolved Version: N/A Added: Mar 13, 2020 |
|
| 225409 |
JUnit XML report is not generated due to a VI Path error.When using LabVIEW CLI Unit Test Framework commands with JUnitReport, if there is a VI Path error, for example -25240: "The path to the VI under test is invalid." the report XML is not generated at all. This will happen even when most VIs are found/tested, but one of them has a bad path. Workaround: Check the paths for each VI and ensure all of them are correct.
|
Reported Version: Unit Test Framework 2018 Resolved Version: N/A Added: Mar 13, 2020 |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.