Cannot install LUnit dependency on LabVIEW 2023 Q3 evaluation

[gt-thetic]

I have a clean copy of LabVIEW 2023 Q3 in evaluation mode, on Windows 10 Enterprise evaluation (All in a VM where I have full admin rights). I wanted to try out LUnit before committing to it. After trying to install LUnit from VIPM, I'm given a red triangle saying missing dependency.
When I try to install the missing dependency, I get a message saying that package astemes_lib_lunit_system-1.3.9.17 could not be installed. I have experienced the same issue on a similar installation on fully activated Windows, not in a VM.

[antsundq]

Hi, Thanks for bringing this to my attention. The system package contains the CLI, which is installed into the ../LabVIEWCLI directory and not ../LabVIEW 20xx. I’ll try to reproduce this on my end and get back to you.

Without this dependency, you should still be able to use LUnit without restrictions from the LabVIEW development environment. However, the native CLI interface will not function.

/Anton

[gt-thetic]

Same issue with 1.3.2.17 and 1.2.29.17.

[gt-thetic]

Without this dependency, you should still be able to use LUnit without restrictions from the LabVIEW development environment. However, the native CLI interface will not function.

Thanks for informing me that LUnit still works even after this issue. I can see it in my Tools menu now and can create the 'new test case'.

[antsundq]

Great! Happy testing.

If you need some guidance getting started, there is some docs available e.g. here: https://lunit.astemes.com/10_Basics/

[antsundq]

I'm having problems replicating this issue. Are you still seeing it with the 1.4.x release?

If it is still an issue, we'll need to get some support from the vipm-community.

[gt-thetic]

I've used version 1.4.15.17.vip from the release on github on a fresh installation of LV 2023 Q3 64-bit, before activation, and I still received this message.

I also went to the activated installation of LV 2023 Q3 64-bit where the latest VIPM was version was already installed. I then tried 1.4.15.17 as above, and I still had the same result.

Is LUnit (System) supposed to be included in the downloaded .vip?

[antsundq]

I forwarded the question to vipm forum and Jim explained a plausible reason for this error. Could you confirm if it applies to your situation?

See: https://forums.vipm.io/topic/7841-missing-system-dependency-when-installing-package/?_fromLogin=1

/Anton

[r-good]

I'll confirm that running VIPM as Admin fixed this problem and installed the dependency

[antsundq]

This is now resolved in version 1.4.20 and later by making the CLI operations, causing the issue, into a separate package.