NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How to base a Sequence Call's result on its local variable string?

Solved!
Go to solution

Hello,

 

I'd like to have custom step result strings ("Untested", ConditionallyPassed", etc) for some of my sequence calls.

 

So far, I have two ideas:

 

A) I've created a custom step, so that SequenceCall step type won't override the status expression... How should I define the status expression string of the "Caller" step in my main sequence, so that it will use the value of a local variable within the called sequence?

 

B) How can I affect the status string of the calling step from within the called sequence?

 

Any tips?

Cheers,

Rok

0 Kudos
Message 1 of 3
(164 Views)

I'm not sure if this the best solution but I was able to alter Step Status using SequenceFilePostStep. I also added custom attribute to my step to indicate that I want to overwrite its status.

 

Will this work for you?

Michał Bieńkowski
CLA, CTA

Someone devote his time to help solve your problem? Appreciate it and give kudos. Problem solved? Accept as a solution so that others can find it faster in the future.
Make a contribution to the development of TestStand - vote on TestStand Idea Exchange.
Message 2 of 3
(157 Views)
Solution
Accepted by topic author tavta

For posterity: we realized with Michał, the easier solution is to write an output string from the called sequences directly to the Step.Result.Status of the step that calls the sequence.

 

However, one cannot use the Sequence Call step type, since it overrides the status expression by default, so passing an output parameter string to Step.Result.Status gets overwritten and doesn't work.

 

Solution: use an Action step type and use the Sequence Call adapter. The Action step type does not override the status expression, so, voila:

 

tavta_2-1629888916120.png

 

 

tavta_1-1629888857248.png

Message 3 of 3
(119 Views)