NI TestStand Idea Exchange
TestStand is in dire need of a way to quickly and effectively find broken steps in long sequences.
I'm working on large sequence files which often call and utilize other long sequences. Needless to say, I often need to address steps which have become broken due to code rework. As of now (TS 2017), there are only two ways for me to know if a step will not run.
- Text is red within the Step Settings window.
- Sequence Analyzer reports an Error.
I would like to suggest a third option, one that would be more readily available than either of the other two options. If the step itself was highlighted, text reddened, or somehow otherwise flagged as an error, then the operator won't have to hunt through each of the step settings windows or the sequence analyzer results. All the operator would have to do is open the sequence file and notice that a step appears out of place.
It would be nice if sequences could also show if they have broken steps.
Included is an example of how this might look.
