‎04-27-2018 11:55 AM
‎04-30-2018 06:31 PM
Hi testdesigner,
Could you elaborate on what you mean by terminated and errored? Are you asking how to terminate an execution?
‎05-02-2018 08:48 AM
Please explain the background of that request. TestStand should not alter the test result by forcing a specific "outcome".
Also note that "error" has a very specific meaning for TestStand: The test system itself encounters an issue and is not able to proceed with a normal test run with an evaluation of the DUT.
Errors are induced in case Step.Result.Error.Occurred turns true for the active step.
Terminated is a result of termination of the execution by e.g. Runstate.Execution.Terminate().
‎05-02-2018 09:17 AM
I have a step that checks if there is an error with test equipment. If I find a fault, I want the test sequence to stop and run the cleanup but the key here is I want the overall UUT Result = ERROR or TERMINATE.
‎05-02-2018 09:19 AM
If I terminate the sequence it will not run the main sequence cleanup steps. That is my issue.
‎05-02-2018 09:22 AM
You seem to mixup abort and terminate. Terminate WILL execute all steps in cleanup stepgroups while abort skips even those...
‎05-02-2018 09:24 AM
Norbert B,
Do you know the terminate step statement to terminate the test sequence that will still run the cleanup?
Also, while you mention abort, what is the step statement to do that as well?
Thanks for your help!
‎05-02-2018 09:29 AM
You should not use abort (unless in specific corner cases)!
Anyhow, similar to terminate: Runstate.Execution.Abort()