NI TestStand Idea Exchange

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

Hi all,

 

Currently if you go to File>>New, there is an option to create a New Sequence File, New Workspace File and New Analyzer Project, but no option to create a new Sequence.  Instead you have go to your sequences pane right-click and select New Sequence.  This can be confusing to new users who may be looking in the File>>New menu to create a new sequence.  Why not make this an option?

 

teststand new.JPG

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.

How about a Mac version of TestStand? I understand there is a Mac version of LabView.

The idea here is to have a widow that you can execute expressions while at a breakpoint or paused.   I would also like to be able to execute the expression while not running the sequence.  Many times I am not sure how will be returned by an API expression and it would be nice just to execute it.  I know that not all expressions can be executed outside running the sequence, but many can.  This would be a nice feature so you can test expressions without running the whole sequence.

 

Allow the configuration portion of steps that call DLLs to see mangled function names, such as those generated by many C++ compilers (@Initv, for instance).

TESTSTAND is capable of interfacing so many devices & instrument to a UUT.

 

Incase of ATE(Automatic test equipment), where lot of resources are made available to test the UUT, not all the resources or instruments will be used through out the test for a particular UNIT. Hence there should be facility to select the resources required for particular test, which will be then only initialized & used.

 

For example a simple power device requires only POWER SUPPLY, LOAD & DMM. Where as a data acquisition system requires POWER SUPPLY, DIO & AIO cards & so on.

 

Thus one should only select the resources required for test & hence no need to have init function separately for each sequence. This may sound a bit complicated but It really helps for LARGE ATEs, where optimization is KEY. Same thing can be implemented for TERMINATING resources once test is done.

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.

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 A.vi and B.VI, then these could easily be loaded into testStand as "A-Project 1.vi" and "B-Project 1.vi"?

 

 

Eugene