NI Home > Community > NI Discussion Forums

NI TestStand Idea Exchange

Showing results for 
Search instead for 
Do you mean 
The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!
New Idea

Step highlighting or tagging

Status: New
by Member Jeff_Bruce on ‎06-30-2011 03:32 PM

When working with multiple long sequences it would be nice to bookmark locations making it easy to find where you were previously working.  The bookmark could be line highlighting or an icon on the left gutter.  Bookmarks would be saved with sequence.  Multiple colors or icon would be available.





Context Aware AutoComplete

Status: New
by Active Participant warren_scott on ‎09-10-2013 10:59 AM

Background --

I LOVE the autocomplete feature within any of the formula windows.  Start typing Locals.F, and it allows you to autocomplete to Locals.Foo.


However, if you have Locals.Foo1, Locals.Foo2, Locals.Foo3, etc, you need to keep typing until you get enough to uniquely match the one you want, or start using the arrow keys in the list (or select with a mouse).


The problem is that if you just type Locals.F, the list of items that shows up is the entire list of Locals.*, in the order they are in Locals.*  In reality, once I've typed Locals.F, I should only get the locals variables that start with F, so I don't need to down arrow through all the other Locals.Bar1, Locals.Bar2 that are inbetween Locals.Foo1 and Locals.Foo2 (because for some weird reason I really want the order of my locals variables to be Foo1, Bar1, Bar2, Foo2, Foo3).


So, let's restrict the autocomplete function to only show the items that match what I have already typed, or at least regroup the matching variables at the top of the list so they are easier to select from.


Even better would be to have it context aware.  If the formula I am typing is "Locals.MyNumber = 3.1415 * Locals.F", and Locals.Foo1 is a string, Locals.Foo2 is an array of booleans, and Locals.Foo3 is a number, then it should skip over Locals.Foo1 and Foo2 because the context requires a number.  Foo1, Foo2, Foo3 should all be in the list of items to choose from if I want to arrow up or down in the list (or use a mouse to select), but Foo3 should be the "defaulted" item that is used if I just hit enter after Locals.F.


Make the property loader window resisable

Status: New
by Active Participant MimiKLM on ‎08-17-2013 03:00 AM



Exactly as in the subject.


Sometimes the names variables are long and could be deeply nested into containers.


Now it is difficult to use them as both windows: the main one and Selected are unresizable.


After proposed change the property loader would have all default features(behaviours) as you can expect from the window at this place.


Current situation presented on the picrure below.





Right-Click Insert and Delete Array Elements

Status: Completed
by Member Joe_H1 on ‎10-26-2010 03:50 PM

Right-clicking on an element of an array variable provides options to "Insert Element Before" and "Delete Element" as can be done with LabVIEW array controls and constants.


 Insert Delete Array Element - Final.JPG

Status: Completed
With the release of TestStand 2012 a number of enhancements were made to increase the drag-and-drop functionality of arrays within the Variables pane, including the ability to be able to delete elements. For more details on this new feature, check out the "Manipulating Array Elements and Array Element Values" section in the NI TestStand 2012 Help under What's New in TestStand>>TestStand 2012>>New Features. Thanks for the feedback! Lars

Tool to create Sequence from Highlighted Steps

Status: New
by Trusted Enthusiast on ‎08-04-2010 01:38 AM

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.


It would be helpful to be able to change the font colors that are displayed for steps in the sequence editor.  This would allow users to identify steps quicker for more efficient editing and debugging.




Please highlight the skipped steps ...

Status: New
by Active Participant manu.NET on ‎07-07-2013 02:24 AM

Hello all TestStand users,


How often i had to debug my sequences ... to find out after many minutes that some of my steps are Skipped ! :smileymad:


It would be nice to highlight the skipped steps by default ... (Without having to customize something in TestStand) :smileysurprised:


  • By using a stroked font to view the step détail (STEP SKIPPED:smileywink:
  • By using a red, flashy color (STEP SKIPPED):smileyhappy:
  • Or better, both ... (STEP SKIPPED):smileyvery-happy:


Thanks for your help ...



Add Quick Drop to TestStand

Status: New
by Active Participant Manooch_H on ‎06-22-2011 03:43 PM

How many of you would benefit from the addition of a feature similar to LabVIEW's Quick Drop?

The functionality that initially comes to mind would be typing to search for your desired step type or step template and dropping it into the sequence you are developing. Please add comments for any additional functionality you might like to see in a TestStand step Quick Drop (for example, you may want TestStand to automatically navigate to the Step Properties of a step after it is dropped from Quick Drop).

Please also add comments for any other situations/scenarios (outside of adding steps to a sequence) where you might benefit from a Quick Drop-like functionality. Thank you.


Ability to create user built-in StepTypes

Status: New
by Active Participant j_dodek on ‎07-05-2010 01:51 AM



I think this Thread should be placed here.


The aim of this is that users can create the same powerful steps like that once which comes from NI.

Biggest enhancement of this would be that i can get rid of the "edit" - button and there is no floating panel

somewhere else.

The second enhancement is that i may use drag and drop between the edit and variable panel (if this is neccessary).


Like Manooch_H I am interrested in comments, too






Define Variables as Constant

Status: New
by Trusted Enthusiast on ‎06-19-2010 03:19 PM

It would be nice to beable to define a variable as constant.This could apply to Locals, FileGlobals, StationGlobals.


Once set mark it so as to be easily identifible as a Const.


The API would also need to include either a Property or Method so that one could determine if a variable is a Constant.




User Defined Expression Functions

Status: New
by Trusted Enthusiast on ‎06-14-2010 02:00 AM
Wouldn't be nice to beable to define one's own set of Expression Functions. This seems to be the one area of TestStand that cannot be customised. eg. = NameOf(Step), Locals.IsValid = DoSomethingNotDefinedByDefaultFunction(,.....(carry on with expression) Regards Ray Farmer

See last changes at Undo Button

Status: New
by Member TobiasT on ‎03-30-2012 01:04 AM

During development of sequences I often do "trivial" changes in order to check parts of the sequence that I do not want to save afterwards  (e.g set Run Modes of steps to Skip). It would be very helpful to see the last changes that can be undone before clicking the Undo-Button arrow (the same applies for the Redo Button of course). This feature would have two major advantages, since one could...

  • ... decide whether it makes sense to save the last changes or whether those were only for trial reasons and hence should be neglected
  • ... undo several changes in one step

This is implemeted in Microsoft Office programs for example (see screenshot from MS Excel) and I use it there pretty often.


Intelligent Variable Creation

Status: New
by Member flaborde ‎02-12-2013 10:49 AM - edited ‎02-12-2013 11:06 AM

The menu to create a new variable (right click on variable in an expression edit control and select Create "VariableName") contains all the data types you can use for the variable, however, in the LabVIEW Panel (and other similar panels or dialogs) there is enough context information about the variable to suggest a data type, for example, if the variable is in a control of type Double we know we should create a Numeric variable. TestStand should add the contextual suggestions to the top of the context menu and bold them so that I can more quickly select the data type I want most of the times, then have a separator and put the normal menu so if I don't want that data type for some reason I can still choose the other data types (see attached image).

When you set the Post Action On Pass | On Fail in a step to use Call sequence, the only ways to pass data to this sequence is either use some sort of Global (StationGlobals / FileGlobals) or use Locals with the setting "Propagate to SubSequence".


There should be a cleaner way and that is to beable to pass parameters as you do with SequenceCall step type.


new Post Action.PNG




Ray Farmer



Expose the sequence file version number to be visible in the file properties. (select file in windows explorer -> right click -> properties -> details).


When for example we do right click -> properties -> details tab on .dll assembly we see:




When we do the same on the .seq file we see:




Exposing sequence file version number can simplyfy checking  version file number. Now to chek it we have to open sequence file in editor.




Beable to Group variables

Status: New
by Trusted Enthusiast on ‎11-08-2011 01:38 AM

When there are a lot of variables defined an Sequence / Sequence File, it would be nice to beable to group them to help use and readability.



Allow to copy & paste ALL values from a container from one step to another step

Status: New
by Knight of NI ‎07-26-2013 11:03 AM - edited ‎07-26-2013 11:14 AM

The MOST annoying part of working with TestStand is the fact that the developer has to re-enter e-v-e-r-y bloody value for a given parameter when the prototype changes in a LabVIEW VI. 


As a sister idea to this one, what is more annoying is the fact that when the container exists for a previous step and is already populated with all the values that you want to repeat elsewhere, TestStand does not allow you to copy and replace a parameter!  Unless there a non-obvious way of doing this (I will attempt a few unorthodox ways to get this done).  If so, it should be an obvious method and not something that requires contortions to accomplish a simple copy & paste. 




Even if the copy & paste could be done from within the parameters, ie: ability to select multiple values and paste them all into the parameter.  This is such a basic feature is most or all programming languages and applications that I cannot believe it does not exist in TestStand. 


In this particular case, the values are from Locals. variables.  And there are lots of them; between two parameters, over 300!!


Let's get on with the times!!  Improve the copy & paste feature, even for an ultra basic request like the one Ray Farmer requested in 2011..  See this link:



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.



Having the ability to have line numbers for all steps in the left hand gutter would help in troubleshooting, code reviews, and any time when communicating about a sequence.  There seems to be a gutter there already, so adding there seems to be a place for them already.  Error messages can also post the line number too.



Step Types for NI-DAQmx

Status: New
by Member Peter_Cooper on ‎03-23-2012 12:59 PM

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. 

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.

Idea Statuses
Top Kudoed Authors
User Kudos Count