Stop the results window from showing at the end

[Believer]

This may seem like an odd request, but is it possible to stop the final results window coming up at the end of the test run? I still need all the results handling mechanism working because results are logged to a database and I use the MainSequenceResults property. However I don't need the actual TestStand results. I'm happy to modify the process model but can't find the right place.

Thanks,

Ronnie

[j_dodek]

Hi Ronnie,

Sorry, I have no answer on this. But i am forced with the same issue. I my case i need it !!!

When i did some tests trying to switch from TS 4.0 to 4.2. I realized that my (Xml)Results in

 Editor and OperaterInterface are missed ! (Internet-Explorer) Control is missing the result's file.

I am using an old TS2.0 derivation of the ProcessModel which has been only optimized over ther years.

There where no Problems on 3.x and 4.0, 4.1.1   

I have compared my model with the model shipped with TS 4.2,  but i found no major difference.

Unfortunately I had no time and money to spend more time on this issue. I put it off to next year topic list.

So i am very courious on the anwers on your thread

Greetings

Juergen

[RayFarmer]

Hi,

There maybe a Engine.PostUIMessage(UIMsg_DisplayReport) somewhere at the end of the ProcessModel entry point sequence or at the end of the Test Report Sequence.

Otherwise you might have to modify your UI.

Regards

Ray Farmer

[j_dodek · Accepted solution]

Hi Ronnie,

I had some minutes time to visit Ni's SequentialModel

If you skip the attached step, no result will be displayed

Hi Ray,

I will try it, but changing UI make so sense because it also happens in the editor

Regards

Juergen

[j_dodek]

Hi Ray,

I have tried PostUiMessage at the end of my EntryPoint.

No report is viewed.

Juergen

[Eric_B.]

Ronnie,

Juergen is correct, if you skip the Set Report step in the Entry Point you are using (Test UUTs or Single Pass), then the report string does not get attached to the execution, and therefore not displayed.  This just shows the completed execution and the report tab contains a blank report.  Is this what you're looking to do?

[Eric_B.]

Juergen,

Between TestStand 4.1.1 and 4.2, the XML reporting was modified.  New XML stylesheets were included that are easier to modify and maintain, and we now encourage people to edit those stylesheets to change the look and feel of their report.  I would take a look at the new stylesheet (if you're still using the TestStand default stylesheets) and see if there were any modifications there that may prevent your report from displaying properly.

Does an XML report file still get generated and it just doesn't display properly?

[Believer]

Hi Juergen, Eric, and Ray,

Greetings from Southern California.

Thank you for all the good advice. Yes - I am using the Sequence Editor, and I decided to skip the Set Report step.

[I should have seen this myself - sorry!].

In an ideal world I would not have the grey window at the end - but no problem.

Thanks for all the effort you guys put into this community.

Ronnie

[James_Grey]

Re: In an ideal World

I'm thinking that

RunState.Execution.TypeMask |= ExecTypeMask_CloseWindowWhenDone

should close the window. However, I tested it, and it does not. I created a problem report on the issue.

[Believer]

Thanks James - good to know!