NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand Termination Reason

I have some Monitoring Sequencec in TestStand, which run in parallel to the actual test.

 

If for example humidity is too high or an error at the PLC occurs, i use the "Runstate.Execution.Terminate()" and add some Info to the UUT.AdditionalData.

However, the result looks the same as "manually" terminated tests.

 

Is there a better way to cancel executions in a parallel thread? Do i need to poll some global in my actual test?

The result is, that the user has no idea why it was terminated and needs to specifically look for some field in the header.

 

THanks in advance.

Message 1 of 3
(168 Views)

Termination always implies that cleanup sequences are executed.

So you could have something like a termination reason / source StationGlobal

which get logged as an additional result to your report during cleanup of your TestSequence. 

 

If you are using a  StationGlobal, just make sure you're not running in a Race Condition!

Message 2 of 3
(146 Views)

Customer accepts it so far that the reason is put into the header.

 

I think if i would go for a global and add a fifth dialog in the DoPostUUT Call to present another result with a PreCondition.

Gert_0-1718707011493.png

 

Thanks for your reply.

Message 3 of 3
(108 Views)