Run LabVIEW unit tests via the LabVIEW Unit Test Framework CLI and report pass/fail/error using standard exit codes.
Common parameters are described in Common parameters.
string
): LabVIEW version for the test run.string
): “32” or “64” bitness of LabVIEW.None.
GitHub Action inputs are provided in snake_case
, while CLI parameters use PascalCase
. The table below maps each input to its corresponding CLI parameter. For details on shared CLI flags, see Common parameters.
Input | CLI parameter | Description |
---|---|---|
minimum_supported_lv_version |
MinimumSupportedLVVersion |
LabVIEW version for the test run. |
supported_bitness |
SupportedBitness |
“32” or “64” bitness of LabVIEW. |
gcli_path |
gcliPath |
Optional path to the g-cli executable. |
working_directory |
WorkingDirectory |
Base directory for the action; relative paths are resolved from here. |
log_level |
LogLevel |
Verbosity level (ERROR|WARN|INFO|DEBUG). |
dry_run |
DryRun |
If true, simulate the action without side effects. |
$json = @'
{
"MinimumSupportedLVVersion": "2020",
"SupportedBitness": "64"
}
'@
pwsh -File actions/Invoke-OSAction.ps1 -ActionName run-unit-tests -ArgsJson $json
Alternatively, load arguments from a JSON file:
pwsh -File actions/Invoke-OSAction.ps1 -ActionName run-unit-tests -ArgsFile ./config/run-tests.json
- name: Run LabVIEW Unit Tests
uses: LabVIEW-Community-CI-CD/open-source/run-unit-tests@v1
with:
minimum_supported_lv_version: '2020'
supported_bitness: '64'
0
– all tests passed2
– tests failed3
– g-cli or test run errorFor troubleshooting tips, see the troubleshooting guide.