LabVIEW Test Executive Support
Test Executive Toolkit 5.0 Troubleshooting Guide
Note: Although this version of the Toolkit is called Test Executive 5.0 it was written for LabVIEW 4.1.
National Instruments later released LabVIEW 4.1. In addition to the improvements to LabVIEW, significant improvements to the Test Executive Toolkit itself became possible.
Improvements in LabVIEW made it possible to increase the execution speed of the sequence file.
Speed is often important in the testing process so this improvement alone made it worth
releasing a new version of the toolkit.
The ability to add subsequences to the sequence was also added in this version of the Test Executive. Previous versions had always been restricted to a single sequence for all of the steps.
Another improvement that was added to this version of the Test Executive toolkit was the ability to call C code as the code module for a step. Previously, only VIs were able to be called as a code resource for each step. This ability was added for UNIX and Win32 platforms.
The Test Executive Run-Time Engine that is shipped with this version of the Toolkit is built in LabVIEW 4.1. All VIs that are called as part of a step in the Sequence Editor need to have been saved as LabVIEW 4.1 VIs. This means that either the VIs were originally written in LabVIEW 4.1, or they have been mass-compiled into LabVIEW 4.1.
