This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

How Do I Resolve the Unit Test Framework (UTF) Crashing When Testing Migrated LabVIEW Code?

Updated Sep 30, 2025

Reported In

Software

  • LabVIEW

Issue Details

I have migrated LabVIEW code from an older version of LabVIEW. When I test it with the Unit Test Framework (UTF) in the later version of LabVIEW (e.g. 2025 Q3), the UTF crashes. How do I resolve this issue?

Solution

Crashes of this type can be attributed to a number of issues. There are common steps that may resolve the issue. They are:

  • Mass compile the LabVIEW you migrated to the later version of LabVIEW.
  • In the Project Properties >> Project dialog, check the Separate compiled code from new project items checkbox.
  • Project Properties dialog.

You can also enable additional logging in LabVIEW. This may help you identify where a problem exists. For example, VIs that did not mass compile correctly. To enable additional logging add the following tokens to the LabVIEW ini file:

  • debugging=True
  • LVdebugKeys=True
  • DPrintfLogging=True
  • NIER=True
  • NIERDumpType=full

These tokens, will generate more verbose crash dumps, which may be useful for further analysis. They also enable more verbose logging to the following log file, which may help with to identify the issue:

 

  • %temp%\LabVIEW_[bitness]_[version]_[user]_cur/log.txt

It should be noted that logs are a tool to help with identifying an issue and my not contain the information we need.