Creating an Executable Version of the LabVIEW Test Executive Toolkit
Primary Software: LabVIEW Toolkits>>Test Executive
Primary Software Version: 5.1
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Toolkits>>Application Builder
Problem: How do I create an executable version of the LabVIEW Test Executive Toolkit?
Solution: In order to distribute Test Executive 5.1.1 with LabVIEW, you will need to rebuild the Operator Interface.
- Launch LabVIEW and creat a new VI.
- Go to the block diagram and insert as SubVIs the following VIs:
- From Callback.llb
- Close Sequence Callback.vi
- Configure Test Vi Callback.vi
- Exit Callback.vi
- Login Callback.vi
- Open Sequence Callback.vi
- Open Test VI Callback.vi
- Per-UUT Logger Callback.vi
- Post Run-Loop Test Callback.vi
- Post-Step Callback.vi
- Post-UUT Callback.vi
- Post-UUT loop Callback.vi
- Pre-Step Callback.vi
- Pre-UUT Callback.vi
- Pre-UUT Loop Callback.vi
- Save Sequence Callback.vi
- Select Sequence Callback.vi
- Sequence Report Callback.vi
- Test Failure Callback.vi
- Test Report Callback.vi
- Test String Callback.vi
- From Operator.llb
- Test Executive.vi
**at this point, if you are using Database Logging, use all of the VIs from step a) above and instead of b) include from LabVIEW Folder\LVEXEC51\DATABASE\Operator.llb:- Test Executive.vi
**and from LabVIEW Folder\LVEXEC51\DATABASE\Callback.llb add:- Create DB Tables Callback.vi
- Per-UUT DB Logger Callback.vi
- Click on the File » Save With Options and select Development Distribution. Be sure to check include vi.lib files. Click OK and name your library. (Suggestion: name it hierarchy.llb, since the INI file attached refers to this file.)
- Launch the Application Builder in LabVIEW 5.1.x.
- Name and specify the File Path. In the Source Files tab, Choose Test Executive.vi as the top level VI (located in the C:\Program Files\National Instruments\LabVIEW\LVEXEC51\operator.llb, or if you are using the Database Logging option from C:\Program Files\National Instruments\LabVIEW\LVEXEC51\DATABASE\operator.llb).
- Choose Sequence Editor.vi as a dynamic VI (located in the C:\Program Files\National Instruments\LabVIEW\LVEXEC51\engine.llb).
- Choose Please Wait.vi as a dynamic VI (located in the C:\Program Files\National Instruments\LabVIEW\LVEXEC51\engine.llb).
- Choose the library created in step 3 (hierarchy.llb) as a support file.
- serpdrv and daqdrv (new NI-DAQ driver doesn’t need the daqdrv) are loaded as default support files by the application builder.
Notes:- If after building and launching the executable, it asks you to find any VIs, browse to the hierarchy.llb to find the VIs it is prompting you for.
- It is very important that all of your VIs are in the same version. To ensure that, mass compile the LabVIEW folder and also your Test VIs.
- You will also need to repeat the procedure on steps 1,2 and 3 with your test VIs. In other words, creating a new VI, placing in the block diagram all your Test VIs and creating a Library.
- You may also need to copy VIs from vi.lib and instr.lib to the installation directory of your executable.
Example: If you are using DAQ VIs, and let’s say you installed the Test Executive.exe (you created using the steps above) in the folder C:\Program Files\TestExec\. You may need to copy the folder C:\Program Files\National Instruments\LabVIEW\VI.LIB\DAQ\ to C:\ProgramFiles\TestExec\VI.LIB\DAQ.
Attached Files (below):
DBHierarchy.vi - With all the VIs needed to create the Hierarchy.llb for Database logging.
DB Test Exec.ini - For database logging, rename to testexec.ini and place it in the same folder you have placed the executable.
NODBHierarchy.vi - Includes all the VIs needed to creat Hierarchy.llb without Database logging.
NODBHierarchy.ini - For non-database logging, rename to testexec.ini and place it in the same folder you have placed the executable.
Related Links:
Attachments: 
Report Date: 06/05/2001
Last Updated: 06/14/2004
Document ID: 2A49BQ6F
