NI TestStand Idea Exchange

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

A coworker of my is taking the TestStand training for the first time and I asked him what he thought.  He has been developing software in Visual Studio for some time now (C#,, etc).  One of his feedback was the extra steps needed to create variable seemed excessive.  His point gave me an idea that I thought would be very nice to have.


Currently, in the expression editor, when you start typing there will be a small popup suggesting existing variables to select.  Wouldn't it be nice that it also gave you the option to create the variable right there.


Say for example I'll need to place my module return data into a variable but I didn't think ahead and create a local variable.  Now, I am in the expressin editor and I start typing 'local.' and then the name of my none existing variable "newVar".  The little popup that shows the existing varialbes detects that what I've typed doesn't exist and gives me a new button where I can create it and assign a data type.  No going over to the variable editor window...



I'm frequently missing that steps are skipped when running sequences. It would be handy to see a steps' background color change when the run mode has changed to skipped or forced pass/fail.



Default log option for " Numeric Array - Graph" , String Array - Array but not formatted properly. Will be good if theres a option to display as table.


TS - Array.PNG

I would like the capability to be able to create my own customized dash board for my own custom step type.  For example,  I would like to create controls (Radio Buttons, Text Boxes, Tabs) on a form that looks similar to the "Call Executable" Step Type. (See Picture 1 attachment). In the default matter, I realize that TestStand allows only 1 button to be inserted on the Custom Step Type Settings Palette for a custom step type. Sure I can create my own custom GUI that allows the sequence file developer to enter the appropriate data in for the custom step type.







Now the Evaluate() command cannot resolve names when the name to evaluate is within the square brackets []. In other words if the name to resolve is a part of the index.


It would be demanded the Evaluate() doesn't have this limitation.  



It's a very likley to happen that during the test the one LV module is called more than one time. As well it is very likely to happen the during the development we have to modify the module itself by changing the input/output from the VI or the connector pattern of the VI. If we have to Reload VI Prototype in one or two instances it's fine but when the step is in more than two or three places it is very painfull to update all of them.


So, I'm proposing to extend the Step Settings-->Module menu by adding the button with action Reload VI prototype in all instances.



As in the subject. Now when you would like to do new line by hitting the enter, whilst you are in the Expression Browser - > Expresion field (marked with yellow), the Expression browser gets closed.


It would be good for visibility if the new line creation would be allowed in this field.





Exactly as in subject.


When code modules containing termination monitors receive the terminate signal, the arrow still pointing at them eventhough the current action is one of the action from the clean group.


It'd be good if the developers and operators could see the current operation as it is in real, not the last active from before termination.





To restore a Teststand perspective to its original layout.

I had an entire test created in TestStand that used the String Value Test step type extensively. A labVIEW VI was called and the test step looked at a String output to determine whether the step should pass or fail. This worked well, however...


After the test creation was complete, the VI that was being called was modified to include an additional boolean output parameter that indicated a special situation where the test should fail. So, all of the test steps had to be converted from a String Value test type to a Pass/Fail test type (which evaluated an expression comparing the original strings and also whether the additional boolean output was true or false.


Since there wasn't really much difference between the two types, I expected this to be rather trivial. Instead, I had to re-create every step in the entire test (that this affected, of which there were hundreds) because there doesn't appear to be a way to change a String Value test to a Pass/Fail test.


If there was a way to simply switch to a different type of validation (such as from a String Value test to a Numeric or Pass/Fail test), then you wouldn't have to re-create the step name, VI selection (and variable setup), pre-conditions, post-conditions, post actions, additional results, comments, step settings, etc. This was quite a lot of work for what seemed to be such a simple thing!


I've been frustrated by this before as this situation occurs on regular basis (although usually only a step or two at a time), but this latest episode required almost a complete test rewrite.

LabVIEW executables update to the Windows settings when run.  So, if the scrollbar size is increased (as is helpful with touch panels), the scrollbars adjust.  However, TestStand called LabVIEW modules running under the Run-Time Engine do not update in size.  This makes it hard to customize the value to the user's needs.

I'm often traversing through many subsequences (both separate and contained), and I'd like a "back" button - just like the one in Requirements Gateway - so I can quickly move back through the list.  A "forward" button might be useful too I guess, but I'd be more keen on getting a "back" button first.