test stand no pass/fail banner and html report

[trout00]

I ran my TestStand sequence OK, then I click aborted, now my sequence ran but the PASS/FAIL banner does not display anymore and the test report is empty when I launch test report. I did not change any code!!! I try to run the examples accessing array, the pass/fail banner still there and the report html works fine.

What do I suppose to do to get the pass fail banner and report html back?

[Elaine_R.]

By default, the pass/fail banner and result logging should always happen when you select to run a test in "TestUUTs." Some of the report behavior can be controlled through the Configure>>Report Options menu. The other alternative is that somehow for this test sequence the processmodel callbacks are not running as they should, either because they have been overridden by a sequence file callback, or that the processmodel has been changed.

In this case I think using tracing would be a good way of debugging this change of behavior. Try and place a breakpoint at the end of your sequence and then 'step into' the process model. Trace through the steps of the TestUUTs proceedure and pay attention in particular to what happens when you hit the steps "PostUUTCallback" and "Te
stReportCallback." If you have not changed your code, and you are executing the correct model and entry point than neither of these subsequences should be skipped and you should see correct behavior.

-Regards

Elaine R.
National Instruments
http://www.ni.com/ask

[Carlos L]

You may also look at the Knowledgebase titled "No Report Is Generated when My Sequence Fails". This is its URL:

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/ccce1e3061100bce86256b5800474375?OpenDocument

After aborting the sequence and running it again, it may be that the sequence is failing for some reason. If this is the case and you have the Station Options set to "Always Goto CleanUp on Sequence Failure", this is the exact behavior that you would have (no pass/fail banner and no report). The easiest solution is to simply uncheck that option ("Always Goto CleanUp on Sequence Failure"), but the knowledgebase gives you other options and an explanation of this behavior.

Regards,

Carlos Leon