10-21-2014 07:20 AM
Hi,
I am using SequenceFilePostStepRuntimeError & SequenceFilePostStepFailure
in my seq file to handle both.
the issue at hand is that, once there is error the execution runs to runtime-error (SequenceFilePostStepRuntimeError) thats fine then again i run my Test-Step & error is generated & it again jumps to runtime-error { Test-Step is a Pass/Failtest}
but after that it jumps to SequenceFilePostStepFailure. I want to avoid this. can I reset the flag which says that no PostStepFailure ?.
In my Runtime-error step I also change the "Parameters.Step.Result.Status" to display my custom status .
10-21-2014 07:58 AM
@aparab wrote:
[..]
In my Runtime-error step I also change the "Parameters.Step.Result.Status" to display my custom status .
Do i understand this sentence correctly if a state:
In your SequenceFilePostStepError callback, you change the status of the step calling into that callback because of a Runtime Error (Status: "Error") to the status "Failed"?
If so, it is expected behavior, no, it even is "works as intended".
You can use the TS API to disable the PostStepFailure callback, but you cannot enable this callback in the same step. So it would require an additional step for enabling the Failure-callback again which seems to makes things more complicated compared to NOT setting the step' result to "Failed"....
Norbert
10-21-2014 08:17 AM
Thanks Norbert,
You got it right.
I change the status as "Error 5506 Motor Fault" & not as "Failed"
I know if the Status is "failed" it will call the SequenceFilePostStepFailure callback.