Setting RunState.Caller.Runstate.SequenceFailed = False in SequenceFilePostStepFailure

[dware83]

Hi All,

I'm trying to use a suggestion from another post in the forum to reset the Main Sequence to a pass during a special condition where we try again after reinserting our DUT which requires us to power down and start the whole main sequence again (hence not using looping):

"The RunState.SequenceFailed property is set if the "Step Failure Causes Sequence Failure' property is enabled in the Run Options section of the step settings. If you're manually changing the step status, you should also set the SequenceFailed property appropriately. Try something like 'RunState.Caller.RunState.SequenceFailed=False' in the SequenceFilePostStepFailure callback."

My problem is that when I try to implement this 'RunState.Caller.RunState' is an unknown variable or property name. I'm wondering if this has to do with the version of Teststand that I'm using, which is TestStand 2016 SP1 (16.1.0.52) 32-bit. If this is not a version problem what might I be doing wrong?

Steps Taken

1) From Main menu bar I click EDIT>Sequence File Callbacks>SequenceFilePostStepFailure and then EDIT

2) Once inside the callback I create an IF condition with a statement inside of it that says 'RunState.Caller.RunState.SequenceFailed = False'. As I'm creating this I notice that the second 'RunState' is not a property option from the autofill box that pops up.

I've also tried just 'RunState.Caller.SequenceFailed = False', and while this is allowed with no errors it does not achieve the intended functionality.

[~jiggawax~ · Accepted solution]

So I don't see why yours shouldn't work.  I threw together this little example at it seems to work fine.  Does it work as expected for you?

[dware83]

Yes, it did actually. I may try printing the result of it at the end to see if it does pass, maybe its just the way that we print our result on the test report and reply back to the system that is running our test. I will dig a little further.