TestStand ReportView Displays Incorrect Report

[Venkat Raghavan]

Preliminaries:

 TestStand 4.2.0.134

 Customized Sequential Model, running Single Pass execution

 Reporting Disabled, but with the following options set.

 * Report Format: xml

 * Stylesheet: Custom stylesheet, full path specified

 * "Force Filename to be unique"

In the process model,we have tried two methods:

Method 1: 

* Call the report.reset method with the complete xml string

* Call the TestStand api method Report.GetTempFile

* Call Report.save with filename returned by Report.GetTempFile

Method 2: 

* Call the Report.reset method with the complete xml string

* Calculate the temporary xml file path

* Set the Report.location with location of temporary xml file

* Call Report.Save with location of temporary xml file

At the end of the process model using both methods, the Report.Location (using the Get Property) method is at the expected location.

When the TestStand sequence editor (The LabVIEW operator interface behaves identically) complete the execution, it seems to create another temporary empty xml file, and then proceeds to display it. The "launch viewer" button seems to be linked to the correct file, as it displays the generated xml report. 

My preliminary thoughts are that the ExecutionViewManager that the ReportView control is hooked to generates the second empty xml file. Any ideas on how to resolve this?

[ManLongAtNI]

Hello Venkat,

You mentioned that you had Reporting Disabled. However, it appears you are manually saving a report in the Teststand report API. Are you trying to prevent users from disabling the "Configure Report Options"?

If that is the case, I would recommend configuring user privileges to allow users to Configure Report options, in the User Manager.

Let me know your thoughts.

[Matthew_Kelton]

Glenn,

Reporting is turned off because it was generating some errors in our custom step types and we were not using the built-in reporting anyway.  I had not intended it to be a permanent solution, but here we are.  Basically, we were reusing some reporting code for a LabVIEW Test Engine which uses its own storage in LV2 Globals.  At the end, we generate the propietary XML file.

When we wnet to add a stylesheet for aesthetic display, we found that TestStand was creating a second, blank file.  This was not happening when we were just displaying the raw xml as a text report.  It seems specific to the XML file.  It is happening insiade of TestStand, becaue the file is not created at the close of the Process Model.  After we allow the Process Model to close and complete execution, the file gets created.

We were hoping there may be a quick fix rather than going back and modifying the Process Model to turn Report Generation back on and debug the errors.  But, I am starting to think, base don the work Venkat has done thus far we have no choice to go that route.

Matthew

[ManLongAtNI]

Hello Matthew,

You are correct, the temporary file that is created whenever a .xml report is generated is expected behavior from the code that Venkat was likely using. In any case, it would be recommended to go the route as suggested to go into the Process Model and change the report options accordingly.

[Manooch_H]

Matthew/Venkat -

I believe the reason you are running into this behavior is in fact because you have disabled reporting which means that the Report.StylesheetPath property is not being set.

In the default Sequential Process Model (Test UUTs and Single Pass Entry Points), there is a sequence call step: Setup Report Display Settings. This step will skip if you have disabled reporting. This step is also where we set the Report.StylesheetPath property. Try removing the precondition from this step and see if this changes the behavior.

Please let me know how it goes.