Sign Up

LUnit by Astemes - Toolkit for LabVIEW Download

Unit testing framework for LabVIEW

D Discussion Watch * 7 ↓2,597
 screenshot
Version1.11.2.6
ReleasedAug 28, 2025
Publisher Astemes
License MIT
LabVIEW VersionLabVIEW>=20.0
Operating System Windows, Mac, and Linux
Used By astemes_lib_lunit_parameterized_add_on   astemes_lib_lunit_test_inheritance_add_on   sas_workshops_lib_lunit_for_g_cli   astemes_lib_lunit_cli   astemes_lib_lmock   astemes_lib_lunit_global_fixture_add_on  
Project links Homepage   Documentation   Repository   Discussion

Description

LUnit is a LabVIEW Unit Testing Framework built on the xUnit unit testing model and inspired by JKI VI Tester. LUnit helps you test driving your LabVIEW development and provides the following key features.

- Fast test execution
- Clear and informative results view
- Run specific tests quickly from right-click menu
- Test results visible directly in LabVIEW project explorer
- Instant loading of UI
- Parallel test execution managed by framework
- LabVIEW API
- Support for extenssion through add-ons

LUnit is integrated into the LabVIEW development environment and the functionality is accessed through the Tools->LUnit menu. From the menu, you may create a new tests or open the LUnit UI to run tests. Tests may also be executed directly from the project explorer by right-clicking on a Test Case and selecting Run Test Case... from the menu.

From Quick Drop window (ctrl+space) use:
- Ctrl+L to run all tests within active project
- Ctrl+Shift+L to run all test cases with tests calling into the current VI

There are a few examples installed with LUnit and these may be found through the NI Example Finder using the keyword LUnit. The examples are installed at C:\Program Files (x86)\National Instruments\LabVIEW 20XX\examples\Astemes\LUnit by default.

Documentation is available on https://lunit.astemes.com.

Release Notes

1.11.2.6 (Aug 28, 2025)

Fix issue #27 - Improved results window for parameterized test addon. Clicking a parameter opens the Parameters.vi
Fix issue #30 - Improved details to JUnit xml report format. This resolves issues with more strict JUnit xml report parsers, such as the Dorny Test Reporter.
Fix issue #31 - API now accepts a directory containing tests as input. This means that you do not need to organize tests in a LabVIEW project and can have LUnit run e.g. all tests in a /tests directory. This works directly with existing CLI tools such as LUnit CLI or LUnit for GCLI without any additional updates.

antsundq was a contributor to this release


Recent Posts