NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Error results in UUT Test Pass

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?

LABOR OMNIA VINCIT
0 Kudos
Message 11 of 22
(122 Views)

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?

LABOR OMNIA VINCIT
0 Kudos
Message 12 of 22
(113 Views)

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

 

0 Kudos
Message 13 of 22
(94 Views)

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. 

jimbobaggies_0-1762245940186.png

 

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. 

 

jimbobaggies_1-1762246286558.png

 

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

 

LABOR OMNIA VINCIT
0 Kudos
Message 14 of 22
(82 Views)

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

 

 

0 Kudos
Message 15 of 22
(74 Views)

I did not know you could change this, how would you remove that option for operators?

LABOR OMNIA VINCIT
0 Kudos
Message 16 of 22
(65 Views)

Struggling to get this working, have tried the following.

 

Locals.termState!=1 || RunState.Step.Result.Error.Occurred!=False
Locals.termState!=1 || RunState.Step.Result.Error.Occurred==True
AnyOf(Locals.termState!=1, RunState.Step.Result.Error.Occurred==True)

 Also tried the above with "Step.Result.Error.Occurred"

 

Cannot seem to get it working.

LABOR OMNIA VINCIT
0 Kudos
Message 17 of 22
(59 Views)

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?


Oli_Wachno_0-1762842752827.png

 

 

More info asap

 

0 Kudos
Message 18 of 22
(38 Views)

Sorry for the delay.... 

 


@jimbobaggies wrote:

Struggling to get this working, have tried the following.

 

Locals.termState!=1 || RunState.Step.Result.Error.Occurred!=False
Locals.termState!=1 || RunState.Step.Result.Error.Occurred==True
AnyOf(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?

 

 

0 Kudos
Message 19 of 22
(24 Views)
0 Kudos
Message 20 of 22
(22 Views)