NI TestStand Idea Exchange

About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

Top Authors
Showing results for 
Search instead for 
Did you mean: 

Add the ability to test the sequence status in the precondition builder editor ...

Status: Declined

I'm declining this idea due to lack of community support.



For the moment, the precondition builder editor only allow to check steps status or to create custom conditions.


It would be nice to add a way to test the current sequence Status.


To handle this, i create my own custom condition by using the runtime variables Runstate.SequenceFailed and  Runstate.SequenceError.

The problem is that these variables doesn't exist at edit time.


I think that adding this feature to the precondition builder editor could simplify our work.




1 Comment
Active Participant
Status changed to: Declined

I'm declining this idea due to lack of community support.