TestStand sequnce is failing even though all (actively result recording) steps are passing

[digisaar]

Good morning TestStand experts,

I am facing the situation that I am executing a historically grown sequence, that itself calls a lot of sub-sequences, with each sub-sequnce implementing a lot of steps.

With a new SUT I am seeing the parent sequence failing, even though all sub-sequences and individual steps are passing.

Can someone give me a hint on how to find out, which step is causing the parent sequence to fail? I was thinking that probably there is a step, which has the "Step Failure Causes Sequence Failure" flag set to true in the "Step Settings -> Properties -> Run Options" while it has the "Result Recording Option" set to "Disabled". A first test showed that this is possible, but how would I find out, which step is causing the issue?

Thank you so much in advance
-Michael

[mateusz_owczarek · Accepted solution]

Hi Michael,

Have you tried to enable option "Break on Step Failure" in "Execute" menu?

[digisaar]

Thank you Matheusz.

[mateusz_owczarek]

You're welcome, glad I could help! 🙂