NI TestStand Idea Exchange

Community Browser
Top Authors
Showing results for 
Search instead for 
Did you mean: 
Post an idea



Browsing through NI documentation I could not see whether logging test results in STDF format is already available or not, and for which SW versions.

I believe there must be some updates for NI document (from 2007) under the following link:


Could anyone please clarify the status?


Currently we are looking into the this as it might be very interesting topic to introduce in our production, where we have the following SW running:

- NI Teststand 4.2.1 & 2.0.1

- LabView 2009 SP1


Best regards

Dejan Lisinac



Everytime you want to update the UUT container, the report generation sequence has to be revalidated. Smiley Mad


Please modify these behaviour ! Smiley Tongue


These behaviour could be perhaps modified by adding a sub container in the UUT container : UUT.Custom

These container could be "non typed" in order to be customizable without side effect. Smiley Very Happy


Thanks a lot!

This function returns Boolean type, not a number type.


The words the index of shall be removed.



The description of the round function in option 4 says as below:




However, the round function behaves differently:





I was working on a project which required LabVIEW 2011 and TestStand 2010. The software had lots of LV modules already created. I reused some of them. However, I needed to trim whitespaces in TestStand which were coming from the string outputs of these LV modules. Nevertheless, I was surprised to discover that there is no TRIM string function in TestStand at all. I had to create a simple VI which just trimmed the whitespaces. I couldn't modify the previously created modules because they were used elsewhere and could affect the outcome of the other test systems. Why does TestStand lack this simple functionality?






Have an option in Report Options to modify report format. 


1. A new tab "Report Format" which can provide the option to generate report in default mode (I call it vertical) or customize to generate in horizontal format.

The Report Format tab can have defined set of options for user to enable in the report. The horizontal format would look like something similar to as shown in the attachment "Report_Horizontal.jpg".


2. Have a checkbox to generate report in Horizontal Format on the "Contents" tab. When selected the report will be generated with the similar table columns shown in the attachment "Report_Horizontal.jpg".



Download All

The sequence editor's (v4.1) diff tool doesn't properly step through the differences if it encounters a "For" loop step or a sequence call step that is a homonym of another sequence call step in the diff window. It basically gets in an infinite loop that can be exited by selecting the next step in the diff window.


Also, if a parameter is added to the parameter list of a sequence and is moved before other existing parameters, the tool doesn't identify the pre-existing steps as identical. It just markes them as deleted from the first sequence and added to the second sequence (therefore it prevents proper comparison).

Having multiple engineers working on code is an issue for me when a person writing an expression doesn't check for errors. I myself am sometimes a culprit of this. The error doesn't show up until Teststand trys to evaluate it, some code will not show errors if the sequence flow doesn't access the step with errors.


It sure would be nice to have a tool that checks for expression errors either in the whole sequence file or a called sequence.

I'm bound to see backlash for this one but here goes!!


The idea exchange, forum and shipped examples are great for learning and resolving specific issues and requesting features and I use them a lot.  But as kind of a newbie what cool things can you actually do?  I'm talking about a different kind of idea exchange for the purpose of sharing what's possible or maybe how some API functions were used to create a particular feature.


Fire away !


There is often problems with cross-linking the wrong LabVIEW VI code modules. Why not automatically import VIs into TestStand from LabVIEW projects using the name of the LV project as a name extension for each VI in TestStand?


For example, if the name of the LV project is "Project 1.lvproj" and contains VIs named and B.VI, then these could easily be loaded into testStand as "A-Project" and "B-Project"?