NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Error results in UUT Test Pass

When running a test sequence in Operator mode, if a step fails for "Error, visa[...]" or "Error, LabView[...]", the test will exit and in the test result file UUT Result shows the error. However we send the result to our own database and it is showing these as a TEST_PASS, the data is coming from "FileGlobals.TestResult".

 

jimbobaggies_1-1708963643643.png

 

My Main Sequence Cleanup is as follows.

jimbobaggies_0-1708963570880.png

 

Any help greatly appreciated.

LABOR OMNIA VINCIT
0 Kudos
Message 1 of 10
(1,387 Views)

What is your error handling strategy? Terminate on error?

 

0 Kudos
Message 2 of 10
(1,352 Views)

I have three levels of login setup, with operator mode when this happened they only had the option to terminate on error.

LABOR OMNIA VINCIT
0 Kudos
Message 3 of 10
(1,344 Views)

Can you describe, how the FileGlobal Value is logged into the database? 

0 Kudos
Message 4 of 10
(1,332 Views)

At the end of main sequence the following cleanup is run...

 

jimbobaggies_1-1709193253362.png

 

I then have a PostUUT sequence that calls an executable, the exe sends the test result file to our database along with the result from Cleanup - str(FileGlobals.TestResult) which will be either TEST_PASS, TEST_WARN, or TEST_FAIL.

LABOR OMNIA VINCIT
0 Kudos
Message 5 of 10
(1,317 Views)

If you are sure, the data is passed correctly from TestStand to the executable, the issue can probably be found somewhere between the exe and the database.

 

Is there any conversion involved form string to enum? Maybe sth goes wrong there

0 Kudos
Message 6 of 10
(1,299 Views)

Thanks for your response, but I am sure it is happening prior to this as all that happens in this step is the test status is retrieved from TestStand and passed to the database, the test status is set during the cleanup. I believe it is being incorrectly set when a test is terminated.

LABOR OMNIA VINCIT
0 Kudos
Message 7 of 10
(1,247 Views)

When trying to debug this, make sure to have SeqEdit configured correctly

Oli_Wachno_0-1710145055710.png

 

0 Kudos
Message 8 of 10
(1,245 Views)

So I never resolved this issue, even after some support from NI via video call it ended up completely breaking my TestStand setup and I had to uninstall from my system and completely reinstall to get it working again.

 

To recap, during test of a UUT if there is a Fail then SequenceFilePostStepFailure is set to offer "Retry, Ignore, Terminate". If there is an error in the vi rather than pass or fail the "Run-Time Error" box appears. If Ignore is selected then the test will carry on, and at the end a TEST_PASS is recorded.

jimbobaggies_2-1761839117009.png

 

So I surmise this is from one of two places that this happens either in one of the following.

"SequenceFilePostStepFailure"

 

jimbobaggies_0-1761838859990.png

 

or the "MainSequence" Cleanup.

 

jimbobaggies_1-1761838893824.png

 

Any help would be greatly appreciated.

LABOR OMNIA VINCIT
0 Kudos
Message 9 of 10
(52 Views)

Trying to understand your issues:

 

On StepFail

 

If a step fails, the User shall be given the opportunity to

- re-run the test --> Question: do you want to discard the failed result? It's in the result list after all

- ignore the fail --> Question: is the UUT Failed in this case? Guess so

- terminate --> Terminate Question: what Status do you expect here?

 

On Runtime Error

 

Even if you click "Ignore" in the dialog box, the UUT Status is Error. DIfferent behaviour must be implemented by the user

 

 

I am referring to the Status as defined in TestStand: Passed/ Failed / Error / Terminated

 

 

 

 

 

 

0 Kudos
Message 10 of 10
(44 Views)