NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Question regarding Parameters.Step.Result.Status

Hi,

 

I'm having some trouble using this particular expression. I'm using the SequenceFilePostStepFailure to set the status of a certain step based on what the user hits in the prompt.

 

So this is how it looks now:

 

Run the VI

Run a sequence to check for failures --------->        Check some numbers

                                                                                     Check some strings

                                                                                     Check an array

                                                                                     Return

 

So if any of the tests in the subsequence fails, SequenceFilePostStepFailure runs. If you hit "retry", I've coded it so that the first VI re runs, and not the step that failed. However, setting the Parameters.Step.Result.Status to "Retrying", doesn't set the VIs status to retrying, but rather the step that failed. The original VI will keep it's status as "Passed" when you re run it.

 

Is it possible to set that VI's status from another sequence? How about just from the next step, like so:

 

Run a VI

<none> adapter (check VI results and set to "failed" if it didn't pass)

 

Thanks for having a look! 

0 Kudos
Message 1 of 2
(2,977 Views)

We had similar issues with designing our tests like this in the past. What we've done to overcome this is to make EVERY test a Multiple Numeric Limit Test and use that as our baseline test. So even if we need to check for a boolean P/F we simply convert it to a 1 or 0 and then use the MNLT step type. Same thing for a string value, we would pass the limit to the test and have the VI return a 1 or 0. This way we don't have to post-process any data and if a step fails we don't run into this.

 

As for what you're seeing it is completely expected. The SequenceFilePostStepFailure callback will occur whenever any step test fails. Based on what you're doing I would recommend changing to the architecture I mentioned above or change the VI to just be an Action step that returns a set of data that you then post-process in the sequence. Then the status would be 'Done' instead of 'Passed' or 'Failed'.

CTA, CLA, MTFBWY
0 Kudos
Message 2 of 2
(2,963 Views)