NI TestStand Idea Exchange

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

According to this forum discussion the Flow step types behave different compared to other step types, making customization hard:

 

http://forums.ni.com/t5/NI-TestStand/Where-does-logic-for-flow-control-step-types-live/td-p/2607349

 

Rectifying the behaviour of the Step types may be out of reach as this would dig too deep into architecture.

But there is a lack of documentation of the behaviour of these steps. E.g. just to mention the fact that step type functionality is in those cases tied to the step type name would help a lot.

Hi,

 

I suggest being able to group steps in a sequence:

 

TS_Group_Steps.png

 

Steps that are grouped should in interactive mode be forced to be handled together, e.g. "Run selected steps" would always select all the steps in the group. This way you could re-use certain steps multiple times down the sequence without allowing such steps to be executed by themselves (or the opposite, make sure certain steps were never executed without surrounding safeguards).

 

Today we'd usually enclose such must-work-together steps inside sub-sequences, but that solution does not safeguard against selecting a single step within that sub-sequence for execution by itself, and sometimes putting steps in a sub-sequence is non-optimal (one such case is when you have disabled tracing into subsequences, but this particular set of steps you'd like to have tracing on - I know there are ways to go about this, but these are cumbersome and non-trivial to spot when editing the sequence).

 

I wouldn't add any extra configuration options to a group, it should simply be a group/ungroup thing - all settings still being on a per step basis.

 

The use cases for a group could be expanded into making it easier to select a co-working set of steps for copying and pasting, it would be a good way to document co-working steps and so on.

 

Cheers,

Steen

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

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

Hola

 

Estoy haciendo un proyecto, que basicamente son rutas o accesos directos a URLs en linea

 

el detalle es que, me gustaria que en mi programa pudiera modificar los URL cuando yo quiera, aun estando ejecutandose el programa

 

esto, porque si llegase a cambiar el link al que me quiero dirigir, lo pueda cambiar desde el el mismo exe sin necesidad de volver a hacer el programa

 

NOTA: los URL los tengo ya registrados en el bloque de diagramas

 

Saludos.

Hello Team,

 

Currently we can’t move or add additional results above the ‘Parameters’ if the subsequence or module has parameter list. It would be useful if we have an option to move the selected result to log in the Additional Results of step settings to desired position/row.

Similary with in the Parameters list, it would be useful if we have an option to rearrage the list.

 

MoveSelectedResultUp.png

Thanks

 

This function returns Boolean type, not a number type.

 

The words the index of shall be removed.

 

4e6b26b26bbed86b21734affadee26.png

Hi,

 

It would be good if the documentation tool would have option/report like described below.

 

After triggering this option user would received the report about every possible flow of the main sequence along with the list of the variables which drive the flow.

 

Value added by this feature:
1. full view about how many flows the sequence is able to be executed,
2. what variables are involved in the flow of the main sequence,
3. general overview about what and when subsequences and steps are executed,
4. where the flows is splited up and merged back.

 

This functionality would be great for sanity analysis and overall picture of the possible executions.

The description of the round function in option 4 says as below:

 

Untitled00.png

 

However, the round function behaves differently:

 

Capture000000.PNG

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