TestStand 2016 unwanted changes in behavior

[Station3]

First question is, what is the most effective way to report bugs in Teststand?

Secondly, I converted a test sequence from TS 2014 to TS 2016.  In this sequence, I have a retest-on-failure feature that no longer worked after upgrading to TS 2016.  There are two changes in behavior that broke it:

1. In TS 2014, when I discard the only failed step from the ResultList stack, the TS engine automatically itself changed the running overall status state to passing.  But in TS 2016, I have to explicitly reset RunState.SequenceFailed to False, and before doing that I have to myself look through the ResultList and make sure that there are no other steps that failed.

2. In TS 2014, in the Post-Expression of a test step, Step.Result.Status would be equal to 'Passed' or 'Failed'.  But in TS 2016 in the Post-Expression, Step.Result.Status is always 'Running'.  So now I have to add a Statement step after in the sequence and read RunState.PreviousStep.Result.Status.

Thanks.   -Joe

[FinchTrain]

Hi Joe,

The best way to report this would be to create a service request with our Applications Engineering Team. This way we can walk through the code more in depth and recreate the issue if needed to determine the cause of the issue, or formally create a Corrective Action Request.

Technical Support

http://www.ni.com/en-us/support.html

Regards,

Finch Train

[Station3]

I reported the two issues to NI tech support.  Issue #2 above is actually a bug fix in TS 2016.  In a step's Post-Expression, Step.Result.Status is supposed to be 'Running' because pass/fail status has not been determined yet at the start of evaluating the Post-Expression.

Issue #1 I believe is a bug introduced in TS 2016.  The app engineer is trying now to check if that's the case with the TS developers.  Actually there is an engine callback sequence named SequenceFilePostResultListEntry with an output parameter named DiscardResult.  If you use that to discard the only failure existing in the ResultList, then the engine should automatically on its own clear the failure in the running overall sequence status.

Thanks.   -Joe

[niarena]

hi Joe! I guess support is already helping you, here there are a couple of documents and an example about the use of that callback, hope it helps.

http://digital.ni.com/public.nsf/websearch/F2D04D7BBC84CFAD86256B14006B8BC2?OpenDocumenthttp://digit...

http://digital.ni.com/public.nsf/websearch/93AA5CF5380F8D5986256F050059A440?OpenDocument
http://www.ni.com/example/29744/en/