NI TestStand

Showing results for 
Search instead for 
Did you mean: 

Capture text file in step result



The sub-sequence I have created uses a Call Executable step type to call an application (.exe) with argument's.

One of the argument's is the location of a log file (.txt), to which a few basic details are recorded.


To set the status of the step I use the StdErr and StdOp values. This works fine and gives a true indication of the .exe's



But if the exe encounter's a problem and the step fails, the only useful information as to the cause of failure

can only be found in the log file (.txt).


I would like to incorporate the log file text into the step's result as opposed to having to search and open the text file 

after the sequence has executed.


It would have been very nice if the step's Additional Results had the option to point to and capture .txt file content.


If anyone can suggest a method to capture the log file text and embed the text content along with the step result

in the report, I would be most grateful.








0 Kudos
Message 1 of 2

The easiest Method is to read text file and map to a variable, now the variable will hold the contents of file. if step encounters error map this variable to log as a result.

Palanivel Thiruvenkadam | பழனிவேல் திருவெங்கடம்
LabVIEW™ Champion |Certified LabVIEW™ Architect |Certified TestStand Developer

Kidlin's Law -If you can write the problem down clearly then the matter is half solved.
0 Kudos
Message 2 of 2