How to disable the temp_report.html generated in test stand

[Gops]

Hello

I have a main sequence file in which, each of the steps is a sequence called with the multithreading option, 'run sequence in a new execution' where each of these step in the main sequence waits for the previous step to end. When I run the main sequence, for each step a new report file is created. But along with it, a temporary html file is also crearted. This file gets deleted at the end of the execution. Is it possible to disable this file generation.

what are the other possible optimisation techniques to be followed for this kind of execution.

Regards

Gopal

[Evan P.]

Hi Gopal,

The report pane displays the execution report using ActiveX calls to Internet Explorer. The generation of this html file is done post execution, and only upon the display of the report pane. TestStand translation of your xml file (I assume you are using the default .xml report generation) into html before viewing is done to enhance performance in certain scenarios. This is unavoidable as long as the report is shown at the end of execution.

One way to avoid this is to hide the execution and disable tracing within it. This is accomplished in Test 4 by checking the Initially Hidden and Disable Tracing check-box within the Sequence Call Advanced Settings Dialog. Now your report will still be generated, but the temporary file will not be created because the report viewer is never active for this execution.

Are you wanting to have the reports on disc, but not view them during execution? If you do want to view the report during execution, it would seem that disabling the generation of this html file is not possible, since the file is generated by TestStand inhereently during viewing.

What piece of this results in you being concerned with performance?

I hope this helps!

[Gops]

Hi,

I want the report on disk. I do not wish to display during execution.

I felt the temp reports affects the performance of the testbench when it is run for longer time.

Regards

Gopal

[Evan P.]

Gopal,

If optimization of execution performance is your concern, I would highly recommend that you run your sequence file using a custom sequence editor, starting with the simple operator interface and editing its code to be as simple (and thus as quick) as possible.

The TestStand sequence editor includes a lot of extra functionality that you are likely not using once your sequence file has been built, using the TestStand user interfaces removes some of this functionality which inherently speeds execution. As I previously mentioned, in order to ensure that the temporary HTML file is not generated, the report view pane must not be accessed. A simple solution to this if you are building you own custom sequence editor is to detach the invoke node that connects the Report View from the ExecutionView Manager.

Another significant performance increase will be seen if you disable the Execution View. Tracing, by its very nature, slows execution considerably.

Both of these modifications will decrease your execution times, while still generating the execution's reports to disk.

I hope this helps considerably in pointing you in the right direction!