NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

test report not visible

I have a LabWindows/CVI program that is using a "system" call to launch the supplied TestStand 3.1 Full Operator I/F and to run a specified TestStand sequence.   The line in LabWindows/CVI appears as follows:
 
                // Create a string to hold the system command string. Note: Command and parameters of the system
                //  command have long file names, so have to build cmd strings that are enclosed in
                //  quotes.  Have to have "nested strings" here.  
                //  Remember that to put a " in a string, have to use the escape, i.e. "\""...
                sprintf(cmdString, "\"C:\\Program Files\\National Instruments\\TestStand 3.1\\OperatorInterfaces\\NI\\Full-Featured\\CVI\\TestExec.exe\" -run MainSequence \"C:\\SCATE\\System Software\\Alignment\\SCATE_Alignment.seq\"");
                sysStatus = system(cmdString);      
 
The TestStand sequence starts as expected running the MainSequence, but when I click on the "Report" tab, I see that no report is generated (on-the-fly reporting is set, but nothing is generated during or after the execution of the sequence).  This happens on more than one TestStand sequence that I tested.
 
If I use a desktop icon to launch the Full Operator I/F and run the sequence, the sequence works properly, and the test report is generated.
 
Any clues?  I'm confused.
 
Harv
0 Kudos
Message 1 of 2
(3,082 Views)
A report is only generated if you use a Process Model.  Since you are running MainSequence without a process model, no report is generated.  You most likely want to use Single Pass or Test UUTs instead.

For example, you would want TestExec.exe /runEntryPoint TestUUTs MyFile.seq

Allen P.
NI
0 Kudos
Message 2 of 2
(3,080 Views)