11-03-2025 02:32 AM
Hello Oli and thanks for your response.
- re-run the test --> The result is changed to Pass, no problem.
- ignore the fail --> Yes that is correct.
- terminate --> if terminated it records a TEST_WARN as per the cleanup in MainSequence.
If Error I would expect to the overall result to be a TEST_FAIL, however it is recoding a TEST_PASS. What do I need to do to make this record a pass?
11-03-2025 07:55 AM
My last response was incorrect, and you cannot edit post by looks of things.
If Error I would expect to the overall result to be a TEST_FAIL, however it is recoding a TEST_PASS. What do I need to do to make this record a FAIL?
11-03-2025 01:49 PM - edited 11-03-2025 01:49 PM
In TestStand, a RunTime Error doesn't neccessarily mean, that the DUT has failed (in dubio pro reo).
So when you perform checking in the Cleanup section, you also need to consider
RunState.SequenceError
11-04-2025 03:06 AM
Thank you again for your help... loving the Latin by the way 😄
When our CM tests product and get and error like this, as they are running TestStand in "Operator" mode they only get the options to Run Cleanup or Abort Immediately, and this is where my cleanup is recording the TEST_PASS.
Thinking about it this shouldn't be a fail as it could be instrument error, comms error, etc, so in the cleanup I would like to add this error state so it gives a TEST_WARN.
Do I need to add in an extra "Else if" statement, or for the existing one can I have
Locals.termState!=1 || RunState.SequenceError.Occurred
11-05-2025 12:02 AM
I don’t see a reason why
@jimbobaggies wrote:
Locals.termState!=1 || RunState.SequenceError.Occurred
shouldn’t be sufficient
BTW…. You are really letting operators use abort? This leaves the system in some state. IMHO it should only be used by a technician who understands the issue and will be able to get the system going / recover to be operational again
11-05-2025 03:22 AM
I did not know you could change this, how would you remove that option for operators?
11-05-2025 04:57 AM
Struggling to get this working, have tried the following.
Locals.termState!=1 || RunState.Step.Result.Error.Occurred!=FalseLocals.termState!=1 || RunState.Step.Result.Error.Occurred==TrueAnyOf(Locals.termState!=1, RunState.Step.Result.Error.Occurred==True)
Also tried the above with "Step.Result.Error.Occurred"
Cannot seem to get it working.
11-11-2025 12:32 AM - edited 11-11-2025 12:33 AM
Sorry, almost (but only almost) forgot about this thread 😉
@jimbobaggies wrote:
I did not know you could change this, how would you remove that option for operators?
More info asap
11-12-2025 11:54 PM
Sorry for the delay....
@jimbobaggies wrote:
Struggling to get this working, have tried the following.
Locals.termState!=1 || RunState.Step.Result.Error.Occurred!=FalseLocals.termState!=1 || RunState.Step.Result.Error.Occurred==TrueAnyOf(Locals.termState!=1, RunState.Step.Result.Error.Occurred==True)Also tried the above with "Step.Result.Error.Occurred"
Cannot seem to get it working.
I tried to think this through, but I'm a bit stuck... which (use) case is actually not working?
11-13-2025 12:04 AM
Just stumbled over this
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x2ZuCAI&l=de-DE