LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Missing UTF file

Solved!
Go to solution

I am using the following:

  • LV 2020 SP f1
  • LV Unit Test Framework Toolkit (UTF) 2020
  • LV Command Line Interface (CLI) 3.1.0(.49155)

as reported by NI Package Manager.
On Windows 10 Pro - 21H2.
I also have LV 2018 SP1 installed, if that matters.

 

When I try and open the RunUnitTests.lvclass ("C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI\Operations\RunUnitTests\RunUnitTests.lvclass") it is missing the file "create junit report.vi"

 

Frozen_0-1642438347783.png

 

Frozen_1-1642438378781.png

 

When I navigate to <C:\Program Files (x86)\National Instruments\LabVIEW 2020\vi.lib> there is no "\ni\" directory. There is a "utf" directory, but it does not contain the file either.
The "utf" directory contains a "Create Report.vi", but junit is *not* one of the options.

 

According to the UTF manual, bug ID: 972908 (JUnit XML report is not generated due to a VI Path error.) is listed in the Bug Fixes.

 

Is there a missing dependency in the UTF distro?
What am I missing? (something simple I a sure)

---------------------------------------------
Certified LabVIEW Developer (CLD)
There are two ways to tell somebody thanks: Kudos and Marked Solutions
0 Kudos
Message 1 of 5
(383 Views)
Solution
Accepted by topic author Frozen

Answering my own question in case someone else is in the same boat...


There is a required dependency to run the the Unit Test Framework (UTF) from the command line interface (CLI) as stated in this Knowledge Article.

 

To quote the article:
"... it is necessary to install the UTF Junit Report library using the JKI VI Package Manager (VIPM) software. To fix this missing dependency install this library using the VI Package Manager or by downloading it from the following link: UTF JUnit Report. "

Hope this save someone else some time and headaches.

---------------------------------------------
Certified LabVIEW Developer (CLD)
There are two ways to tell somebody thanks: Kudos and Marked Solutions
0 Kudos
Message 2 of 5
(327 Views)

Would've been nice if it was in the documentation instead of in a knowledge base article.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 3 of 5
(303 Views)

@billko wrote:

Would've been nice if it was in the documentation instead of in a knowledge base article.


Yes, I was tempted to leave a snarky comment about that 😇

---------------------------------------------
Certified LabVIEW Developer (CLD)
There are two ways to tell somebody thanks: Kudos and Marked Solutions
0 Kudos
Message 4 of 5
(300 Views)

@Frozen wrote:

@billko wrote:

Would've been nice if it was in the documentation instead of in a knowledge base article.


Yes, I was tempted to leave a snarky comment about that 😇


I did it for you so you didn't have to.  😄

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 5
(285 Views)