Issue Details
When running a TestStand sequence with LabVIEW test steps using the LabVIEW Runtime Engine, my code behaves unexpectedly compared to running with the LabVIEW Development System. This issue may show up when deploying the test sequence on systems where only the LabVIEW Runtime Engine is available.
As an example, a LabVIEW VI test step with dynamic paths throws
Error 7 - File not found when using the LabVIEW Runtime Engine. This does not happen when using the LabVIEW Development System Adapter for test step execution. Here, the test sequence and LabVIEW test steps execute as expected.
To get to the configuration dialog, select the TestStand menu options Configure ➔ Adapters...