Halt All Testing on Failure

[Captain_Jack]

Jim,

Also, the method of terminating the sockets individually leaves the batch dialog execution in place with the existing information on the original sockets. This enables the existing non-failing tests to be restarted with minimal fuss.

The only issue is that all of the Sockets will show a status of Terminated (yellow), not Pass or Fail. Pass/Fail information would have to be analyzed in some fashion (automatically or by the operator) to determine who caused the failure and why. If you want to exit Testing of first failure, and still see the overall status, you could set preconditions to Skip tests and/or set Goto's as necessary to get to the MainSequence Cleanup if a failure occurs. Then the status should be easily determined.

Just my .02 on this.

-Jack

[GeekGrok]

Jack,

     Thank you for your reply. I do appreciate your help. I understand your reasons for not wanting to post any code.

     I have a pretty good idea of what you are doing. I have kind of figured out the Terminate/Pass/Fail status. I can look at the ResultList[0].TS.SequenceCall.Status to see the "pre-terminated" status of each sequence call to determine which sequence (i.e. UUT) failed and which ones were passing and then terminated.

Thank you,

Jim