How can I get Test Stand to print failues only?

Question

Rather than getting a large report file with hundreds of passes and only one failure, how do I configure Test Stand to only print the failures to the report?

Answer 1

Hi,
the engine callbacks are simply a sequence that gets called when a particular thing happens (i.e. Post Step).
There's three types
SequenceFile (for steps that execute in that sequence file whether it's a client sequence file or a process model)
ProcessModel (for steps that execute in the client sequence file run under this process model, but NOT the steps in the ProcessModel)
Station (for all steps on that installation - found in the StationCallbacks.seq sequencefile)
If the engine callback appears in more than one of the three places, then the lowest one (seq file->proc model->station listed lowest to highest)is used.
In your case, you could use any of them depending on your architecture.
Personally, r
emoving from the resultlist is easier than working out whether to add to it, but that gets tricky when you have steps which loop.
If you decide to make up your own add, then the PostStepFailure is the callback sequence to use (go to edit->sequencefilecallbacks). You'll have to add a new element to the resultlist, and start fleshing it out with the result container of the step (which you still have access to as a parameter) plus the TS container.
This would go into the Runstate.Caller.Locals.ResultList[x]
Also, don't forget to disable the result collection on all the steps in the test sequence, plus all the ones in your poststepfailure callback, since you're doing your own.
I'm attaching what I've done so far as an example - not quite finished, but it's done the TS container. Just now need to do the actual result container.
I'll keep working on it but for now you can see what I'm getting at.
Hope that gives you a kick start with the callbacks bit
Sacha Emery
National Instrumen
ts (UK)
// it takes almost no time to rate an answer
Attachments:
collect_only_failures.seq ‏31 KB