Stop the results window from showing at the end

[j_dodek]

Hi Eric,

I am using my own stylesheet which is completley different to Ni's one.

I think i will create a new thread on this topic tomorrow because now it is to late in the night.

I will place some more information to my stylesheet.

So please wait.... 

Greetings from Lake of Constance, Germany

and good night...

Juergen

[Manooch_H]

Believer -

If you don't want to create and display a report based on your test results but you want to log your test results to a database, you could simply just check the Disable Reporting in the Report Options dialog. This will prevent a report file from being created and displayed.

This is the recommended approach if you do not want a report. Skipping the step in the Process Model as previously suggested is not ideal because you may later decide that you do want to display a report and will have to remember how you disabled it in the first place. Also, by skipping the step, you're preventing the report from being displayed but it is still being created on disk which may not be what you want.

Hope this helps.

[Believer]

Manooch,

What you said would work if I did not use the MainSequenceResults property. But I do, so it doesn't.

If reporting is disabled - there are no results generated.

Thanks,

Ronnie

[Manooch_H]

Ronnie -

That's not necessarily true. The only time that results would not be generated is if and only if Report Generation is disabled, Database Logging is disabled, and you have checked the model option for Discard Results or Disable Results When Not Required by Model (found in the Model Options dialog, Configure»Model Options).

Hope this helps.

[Believer]

Manooch,

OK - good call - except that the Report window still comes up at the end with 'Report generation is disabled'...

My goal is to stop this window from coming up - but still get results being generated 'internally' so I can work with them.

Thanks,

Ronnie

[Manooch_H]

Ronnie -

What do you mean that the Report window still comes up at the end with Report Generation disabled? Do you mean that the tab is available? Or are you saying that the window comes up in front?

If I disable report generation on my machine in the Sequence Editor, I can execute Single Pass or Test UUTs and when my execution completes, I see the completed steps. There is a Report tab but it is not brought to the front. Are you in the Sequence Editor?

[Believer]

Manooch,

Yes, I am in the sequence editor and the report window comes to the front - and I have to close it. Is this not what you expect?

Ronnie

[Manooch_H]

Ronnie -

Thank you for providing the screenshot. This is actually a difference in behavior caused by the report format that you have selected. It looks to me like you have the ASCII report format selected in which case this behavior will occur even with Report Generation disabled as you mentioned (the behavior is also the same if you have HTML selected as the report format).

If you select XML or ATML as the report format and then disable Report Generation, you will no longer see the report window pop up at the completion of the execution. You can either change the report format to XML or ATML and then disable Report Generation or you can use your current workaround. It's up to you.

Thank you for bringing this to our attention. I will make a suggestion that when Report Generation is disabled, the Report window not be displayed, regardless of the report format and it will likely be corrected in a future version of TestStand.

Thanks again.

Message Edited by Manooch_H on 12-03-2009 03:01 PM

[Believer]

Thanks for the info - and glad to be of some help Manooch.

Perhaps there could be an option to avoid the summary window at the end (my original goal) ?

But then - perhaps that is what a custom UI would be for.

[Manooch_H]

Ronnie -

If your ultimate goal is to close the Execution window once your sequence file has finished executing, in the last step of your executing sequence, call the following TestStand API method:

Thread.PostUIMessageEx(UIMsg_CloseWindows, 0, "", RunState.Execution, True)

This can be called from an expression statement in TestStand 4.0 or later as shown below:

Or it can be called from an ActiveX/COM adapter Action Step as shown below:

Hope this helps.