Using "Single Pass" entry point with sequences not named "MainSequence"

[Sunny]

Hi,

The object model of TestStand provides clustering of multiple sequences in one sequence file. The editor itself allways knows which sequence the user has actually selected (enrty Run ... in Menu Execute is allways fullfilled with the correct sequence name).

Why isn't there any support of using the entry points of the model with this selected sequence, these sequences use the default "MainSequence" if they are called by the corresponding menu entry of the Execute Menu.
I am looking for any solution to use the entry points (by menu calls) with sequences not named MainSequence as well.

Any ideas?

Regards,
Sunny

[RayFarmer]

Hi,

If I have understood your question correctly.
The answer is, there is. Look at the menu item 'Run Selected Steps Using'. This will give a submenu of the enabled Entry Point eg 'Single Pass' ( as default) and Test UUT's (if you have enabled this in the process model).

Regards
Ray Farmer

[Sunny]

Hi Ray,

Your suggestion is a good workaround but you have to select all steps of your sequence before. Is there no way to modify the model entry points that they allways use the actually selected sequence in case of using them with the Execute Menu. I think it is a unexpected restriction, that this works only with the sequence called MainSequence.

Regards,
Sunny

[Scott_Richardson]

Sunny -
In the process model entry point "Single Pass", if you look at the sequence context during an execution, you will notice that the sequence that was visible or "selected" at the time of the execution is started is specified under "RunState.InitialSelection.SelectedSequences[0]". You could alter the MainSequence call step in the process model to call that sequence instead. Keep in mind that you will have to decide how to handle the case when no sequence is selected, do you call MainSequence or do nothing?

Scott Richardson (NI)