06-17-2024 06:34 AM
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.
06-17-2024 07:35 AM
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!
06-18-2024 05:37 AM
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.
Thanks for your reply.