Re: "Remove Backspace" test harness

[Jim K. <jk...@ja...>]

Brian Gangloff wrote:

> 4. Can we create a batch that completely quits LabVIEW between test VI's?

Or even better, how about a LabVIEW executable that controls the 
development environment?

I have been working on a tool called "lvbld" that allows building 
LabVIEW applications (as defined by .bld files) from the command-line on 
the Linux and Windows platforms.  It is an executable application that 
communicates with the LabVIEW development environment using VI Server 
over TCP-IP.  This methodology could possibly be used in the Remove 
Backspace test harness.

When lvbld is run, it attempts to connect to LabVIEW using VI Server.  
If it cannot connect, it launches LabVIEW from the command-line, and 
then attempts to establish VI Server communication until a timeout is 
reached (see "lvbld.ini Settings" section, below, for a listing of lvbld 
settings).  Once a VI Server connection (Application Reference) is 
established a strict VI reference is opened to 
<.\project\prodisttool.llb\_Build Application from Script.vi> which is 
called by reference.  Finally, when all the builds are complete the 
remote application is shutdown, if it was not open prior to running lvbld.

VI Server does not provide any means for shutting down an application.  
But, since both lvbld and LabVIEW share the same file system space, 
LabVIEW can me made to call VIs within lvbld (since LabVIEW executables 
are just glorified LLBs).  A VI called app_exit.vi is included in the 
lvbld exe and contains a call to the "Quit LabVIEW" primitive.  lvbld 
causes the LabVIEW development environment to run this VI and thereby 
causing it to exit.

If you want to take a look at the lvbld source, it is located here:
http://www.openg.org/tiki/tiki-index.php?page=LVBLD+-+Command+Line+Build+Tool

-Jim