NI TestStand Idea Exchange

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

If have to run 10 different UUTs for each group, the TestStand report should contain a either mass header or footer that shows the UUT group statistics, Example: 10 UUTs total run, 7 Passed 3 Failed, in It would seem almost obvious that the TestStand report would contain this information.UUTGroupResults.JPG

 

 

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. 

 

exports2.JPG

 

exports1.JPG

 

 

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.

 

Regards,

 

Kyle Mozdzyn

Applications Engineering

National Instruments 

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.

 

 

SequenceEditorStepHighliting.jpg

When putting values into an array of number local variable, there is little documentation specifying the correct way to input values in an array. The documentation needs to be improve and/or the error message that pops when evaluating your statement should be fixed to better demonstrate the problem. The current error states "Variable or property types do not match or are not compatible. This value will cause a run-time error." A getting started documentation that addresses variable syntax would also be helpful, these ideas will improve ease of use for people working in TestStand. The typical syntax when working with arrays is the use of a bracket [] and the error that appears when using a bracket for arrays is even less helpful. Attached is an image of an example of the fixed error that would demonstrate this problem more thoroughly (The red highlighted section would be a potential change to the errors).

 

Capture.PNG

On this Web page under the New Users are links to the various documentation but these links are not very helpful as there just send you to www.ni.com/manuals which cover every manual for every NI product. You are actually quicker doing a basic search for TestStand manuals than using these links. What should happen is you should be directed to the relevant document. ie for the TestStand Reference manual 2010 you would be directed here.

Hello,

It would be nice to insert comment lines not stuck to steps. In fact often comments lines are not related to a step and it's unlikely that moving a step it drags the comment with it. 

Even though we already have an About box for TestStand, it would also be nice to have one for the active TestSequence file as well. The Help menu would have a new item called "About MySequenceFile ...".

 

MySequenceFile About box splash screen:

19679i37712516107E8A41

 

The information in this screen should be loaded directly from a single FileGlobal string whenever a sequence file is made active. This can probably be done already by those that know how, but it should be already part of TestStand by default.

 

 

Eugene

It would be nice if the Step Settings for a Sequence Call step's Module tab would also list the calling sequences comments field and the parameter comments in addition to the prototype information. This would allow sequence calls to easily present information on the expected use of the sequence, along with parameter information (ranges, default options, etc) that would be useful to the developer. I've created a simple mockup of what I'd like to see here:

 

19657iFA3E1FCBE0E24E08

 

By adding these features, sequences can contain their own 'help' information which would allow the developer to configure the call without having to leave the step module dialog.

 

Thanks,

 

-Jack

A TestStand configuration wizard

 

I would like to see a TestStand configuration wizard that would walk a developer through a checklist of all of the most important configuration settings and generate recommended changes.

 

It is best for a developer to be already familiar with Best Practices as in the following link:

 

Best Practices for Improving NI TestStand System Performance

http://zone.ni.com/devzone/cda/tut/p/id/7559

 

However, it would also be nice to have assistance in recording WHY certain choices are made as shown in this image:

17669iC6E2378DE5CA3B29

 

 

Eugene

Professional Development package should include source code control (SCC) and Requirements Gateway right out of the box.

 

I know that bundled SCC was a problem in the past that NI wants to avoid, but I feel that a "Professional" development system isn't very professional without it and Requirements Gateway. However, It is very difficult and painful for me to get separate funds approved for important items that really needs to be already there right out of the box.

 

I already use free SVN, but TestStand does not recognize it, so it is not "integrated".

 

 

Eugene