Running sequence with operator credentials from custom UI

[Roman Ziak]

Hello,

In my C# operator interface I have the following:

axSequenceFileViewMgr.ConnectCommand(ButtonDoTest, CommandKinds.CommandKind_ExecutionEntryPoints_Set, 0, CommandConnectionOptions.CommandConnection_IgnoreCaption);

When I use index 0, that is like Test UUTs from Sequence Editor, when I use index 1 it is like run sequence, which is not allowed for operators (but it is for technicians). I have found this out by trying, the documentation on CommandKind_ExecutionEntryPointSet and its indexes is non-existent!

My customer insists that we run the sequence with operator credentials.

The problem is that Test UUTs wants to loop. I use sequential model and there is a Locals.ContinueTesting flag. I tried to create the same flag in my sequence Locals and set it to false, but it does not work.

How to run the test one time with operator credentials ?

How does SeqEdit run a test once ?

Thank you

Roman

[RayFarmer]

Hi,

The easy answer is to modify the Operator user previledges so that they can run 'Single Pass'

I think you will find this option in the Execution group of previledges.

Regards

Ray Farmer

[JonP]

For info, the privilege is in the Debug category and is called SinglePass. This problem still applies in TestStand 2019.

This thread does not answer the question "how does SeqEdit run a test once?". If you are logged in as an operator without the SinglePass privilege and select Execute » Single Pass in TestStand it works fine, so how come it doesn't using ConnectCommand()? This is inconsistent in an unexpected way, and just one of the reasons we poor developers waste a lot of time trying to make the poorly-documented API work.