NI TestStand Idea Exchange

Hello,

It should be nice to be abble to view the UIEvents directly in TestStand SeqEdit.

This could be helpfull during debugging a sequence.

The idea could be done like a Debug / Trace window.

It should also be interresting to have such a "UIEvent callback" in the process model. 

Manu.net 

I would like to see the possibility to add Tools (Menu > Tools) to Toolbars. See the recording below:

As you can see from Tools section I can select only "Customize". It could be great to have the ability to use custom tools when customizing toolbars and menus.

I'd like to see a "No Comparison" comparison type added to the String Value Test.

Currently there are only two options for comparison type on the String Value Test: "CaseSensitive" and "IgnoreCase".  I have often wished there was a "No Comparison" option similar to what is available for the Numeric Limit Test.  Sometimes you want to pass a string to the test report in the result field that neither passes nor fails the test.

Hi,

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.

Hi,

Exactly as in subject.

I thought that it will be good if the developers could collapse blocks of code which are in between of the Flow Control or/and Synchronisation step types.

I think about the mechanism we know already from TestStand which hides block of code: i.e. Setup, Main, Cleanup section in the sequence, or it can hide variables. It is a little "+" and little"-" to expand the content of the type of variables.

The types of steps I think of were mainly types from Flow Control and some types from Synchronisation. It would be good if for example we could collapse If-Else-ElseIf-End, Select-End, Case-End, While-End, DoWhile-End, etc statements

I think this functionality could improve the readability of the sequence, and helps the developers to have a better view on the whole sequence.

Hi,

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.

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:

http://forums.ni.com/t5/NI-TestStand-Idea-Exchange/New-Paste-Value/idc-p/2504798#M721

Right now, the breakpoints/watches window  (Debug >> Breakpoints/Watches) is modal against sequence editor.  This makes my life harder because I can't keep that window open to enable/disable a bunch of breakpoints scattered across a sequence(s) during an execution -- I need to be stopped at a breakpoint, open that window, enable/disable other breakpoints as desired, close the breakpoint window, continue execution, and repeat.  I'd like to be able to just keep that breakpoint management window open the whole time (Just like I can with LabVIEW).

Another related thing that would be nice is to be able to manage breakpoints per execution.  At this point I can have multiple simulatenous executions, and I can add breakpoints at run time that are specific to that execution.  However, I can only manage those breakpoints easily through the execution view windows, and not through the breakpoint manager.  It would be nice to see individual executions show up in the tree structure of the breakpoint manager the way each sequence file does.