NI TestStand Idea Exchange

Community Browser
About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

Top Kudoed Authors
User Kudos Count
Showing results for 
Search instead for 
Did you mean: 
Post an idea

In order to keep file clean, sequence analyzer helps in finding "potentially unused variables". To delete such variables, each warning in sequence analyzer result has to be double clicked and then delete has to be pressed to finally remove that variable.


In many cases with large sequence file, there could be dozens of unused variables and in a single work-space there are dozens of .seq files.


Is it possible to provide a button or some option to remove all unused variables from a sequence file?

  • Utilities and Tools

Sometimes it is useful to be able to search for instances of custom data types. Unfortunately, there doesn't appear to be a way to do this in TestStand.  It would be really nice if you could search for instances of types in the Types window or perhaps through the Find/Replace utility:





Almost all of our analog measurements are specified in %: example


a Power Supply DMM measurement limit is 24.00Vdc +/- 5%


We typically have 100+ measurements like this in a project



Why not include it in the default step types as an optional selection?

I sure would use it, so would my team.


I agree that it should not alter existing programs using the default step, but I believe that this feature should have been in Teststand when it was first released.


I have run across this in both analog measurements, and the results from an ADC

Think a limit of 0x234 +3%, -7%



I have noticed that the TestStand shipping examples are often overlooked when looking for ways to accomplish things with TestStand.  This is not the case (as much) in LabVIEW and CVI, and I feel that this is because TestStand does not have an example finder.  I would like to see some method of accessing the shipping examples through the sequence editor environment, such as:



Another problem with the current setup is that the only way to know what the example demonstrates is the name of the folder.  This makes it easy to overlook examples that would be helpful. 


I propose adding a TestStand example finder with these features (in order of importance):


  • Provide a description for each example (most of this info can be pulled from the sequenceFileLoad callback dialogs in a lot of the examples)
  • have keywords for the examples, and allow searching
  • for more advanced examples, provide a batch file to load all necessary components 
  • Provide links to the NI community and developer zone to encourage participation

  • Utilities and Tools

Currently, to export properties which are part of an array, such as the limits of a multiple numeric limit test, you have to specify each index of the array separately, like in the first screen shot, or else you get all of the raw XML, which is difficult to interpret and use. 







This is both labor intensive and unituitive. . If instead we had the option to export the array with the "?" and have it parse the information out like in picture 1, it would be much simpler to use.




Kyle Mozdzyn

Applications Engineering

National Instruments 

NI has gone through a lot work to get the IVI Components integrated within TestStand as step types. I was wondering why NI has not incorporated the NI-DAQmx technology into TestStand as step types. I realize most TestStand developers would just create TestStand Adapters in the sequence step written in CVI or LV to interface to NI-DAQmx functions. Even the more advanced TestStand Developers would create their own custom step types to interface to NIDAQmx. I have just done that to where I have created a framework of custom DAQmx step types that I use as a small subset from all the NIDAQmx functions used from the NI-DAQmx library. 

It would be nice to be able to create a new sequence from highlighting steps in a sequence and performing a right mouse click, "Create New Sequence...", this would be a kin to Create SubVI in LabVIEW.


This action could display a dialog to give possible options such as, to copy the Setup and/or Cleanup group, Create in a New SequenceFile or in Current SequenceFile, the option to Move or Copy highlighted Steps. It could also include creating any locals and /or  FileGlobals (if creating in a new SequenceFile) used by those highlight steps.


currently the behavior of the date function is (1) get a short ("MM/DD/YYYY") or long form date string ("Weekday, Month D, YYYY")with nice easy boolean input, (2) pass it N local variables to get all the discrete parts and assemble it myself with a bit of STR() and concatenation.


could we create a permutation on this date() function, (does one already exist) so that I can just pass it a %<> syntax string and have it format the current date to my desired format?


specifically, I'm looking for a non painful way of building a "YYYY-MM-DD" style string for a report (or even just DD/MM/YYY) without having to lug around 8 locals and a lengthly expression, or call into a LV VI. 


We have basic string format symbols available for the STR and VAL functions, why not for date? if anything passing this 1 parameter might save alot of folks creating a bunch of locals because they can just ask for the time item they want directly, and then VAL() the output text to get the numeric data if they need it?


it'd be awesome if the function supported standard DB format tags such as ( or failing that, was consistent with what LabVIEW's time format strings were.


Just a thought. Has anyone worked around this in a reasonable way?


--Elaine R.

Right now it appears the sequence analyzer has no really effective automation options?


I can use the command line to launch the Sequence Analyzer, but I really want to run this puppy headlessly against a codebase every 24 hours similar to how VI Analyzer works.  Ideally, yes, I'd love a full API, but for the short term, would it be possible to expand the command line?


what we have currently is:

AnalyzerApp.exe "C:\My Documents\MyProject.tsaproj"  to get the window open with the right project in it.

what would be seriously helpful would be to add: some sort of "-Run -Report "C:\Reports\MyProjectReport.xml""  additional tags?


In general I'd love for the tool to (1) launch, (2) run project, (3) save off file, and (4) close without further nagging on the part of a user.


 Extra kudos would be given if it could generate a standard-out message with some quick stats, if someone was feeling really gung-ho. Perhaps a # of rules, run and # of errors & warnings found?  I can just as easily rake the xml output, so these aren't required, but I am in dire need of a way to automatically _get_ that xml output.


If the tool already does these tasks than please feel free to say so?  I've combed the help in the versions I have installed, and so far have come up with nothing. I'm currently shopping around for a thin ui-robot to get the job done...


  • Utilities and Tools

It would be great to have the ability to create an independent TestStand configuration that is valid in a workspace context. That would allow project specific search directories, StationGlobals an several other configuration items you normally don't want to share across projects on the same test station.

I’m trying to work with the tool Requirement Gateway. I started with some examples which are contained in install packet of this tool. I need to connect Gateway with HTML document and manage coverage with another HTML document. I managed to get from HTML document load the list of requirements to Gateway tool. If I tried to open the particular requirement from Gateway than the HTML document was opened on first page always. I can’t set the Gateway for opening the HTML document on particular place, when is described requirement.


My point of view is make some modification for better connection Gateway tool with internet browser.

How cool would it be to sequence any LabVIEW VI in TestStand? I realize one could make a wrapper around any VI, but that adds not only a layer of complexity, but customization. I am a staunch follower of the KISS philosophy, and custom wrappers are not so simple; well, at least not as simple as no wrapper at all ; )

  • Utilities and Tools

It would be nice when entering in the Find: control to beable to pop open the Variable dialog (as in the expression editor) to select variable names. It could be linked to the Limit Search to: control. Like wise on the Replace control when that window appears. 


I know you have that drop down facility on this control but that only remembers what you have previously entered.



It would be very handy to have a jump list of recent/pinned files for TestStand.  This could also include simple tasks like creating a new sequence file.




Current TS.png




Proposed TS.png

The output messages are a good way of sending status messages from the test solution to the end user.  However the control is not available as one of the controls that can be added to user interfaces.


Can this control be made available to be quickly added to a UI and linked to the execution view manager.

Also adding some kind of API interface to be able to capture these messages to a log file would remove the need to implement any custom logging mechanisms.  If possible ability to open multiple file logs within the engine at the same time with each file given some kind of filter rules (for example Severity=”error” or ExecutionId=5).  If logs had to be attributed to an execution ID then they could automatically be closed when the execution ended, otherwise the user would have to manually close each file which could get forgotten and TestStand end up with lots of open file references.

TestStand already has an awesome tool to change multiple steps at one time, but you have to select all of those steps first by clicking on them with the mouse and using the shift and ctrl click methods.  This works fine for a few steps here and there, but when you have 1000 steps you need to select that are scattered among 1500 other steps, it turns into a two day project.
I'd like to see something else that's different than the find/replace window that gives you the option to select and highlight the steps you just searched for in the sequence editor.  It could be a checkbox in the find/replace tool window that gives you the option to either search for the text and display the text matches in that window, or to select the actual steps in TestStand.
I just had this problem, and ended up creating some ActiveX code to automatically blast through my sequence and change hundreds of NumericLimitTest step types to Action step types.  That example code was attached to that thread.

The Sequence File Documentation Tool allows you to create documentation in the file formats HTML and text.


It would be nice if it could also create XML based documentation similar to report generation. Selecting a style sheet will ensure that the XML file is presented in a certain way using a browser.



At our facility, we have a shared Users.ini file on a network that is used by all test systems in our entire organization (somewhere between 150 and 200 systems).  It contains hundreds of different users and many different user groups and its contents change frequently.  I recently upgraded to a newer version of TestStand and learned that a single Users.ini cannot be used by multiple versions of TestStand; it can only be used by the version of TestStand in which it was created (or saved, when upgrading).

This is problematic because it means I have to maintain multiple Users.ini files for the different versions of TestStand in use at my facility; whenever I need to make a user change, instead of changing it in one location, I have to make the same change in multiple Users.ini files.  Because there is a mixture of TestStand versions in use at my facility, it would be really nice if different versions of TestStand were able to use the same Users.ini file.

  • Utilities and Tools

Although BuildTSD allows for builds from the command line, they are still not automatable because someone must be logged in for the run to work. All of our other build tools (Visual Studio, Eclipse, MPLAB, Quartus, NIOS, Matlab, etc.) allow for headless, remote, automated builds which support our move toward continuous integration, continuous deployment, and agile development.

It would be nice if TestStand provided basic file I/O functions (open, close, read, write) to complement the other functions already available.