how do I prevent reporting Button Index line of Message Popup Result in TestStand report??

[StephenGerads]

My Message Popup is reported as:

   Verify that the Installed memory (RAM) is 1.96 GB: Passed

        Button Index:             1

What is the best way to prevent reporting the Button Index line?

[Teds]

It looks like you modified the Message Popup to put a "Passed' status, my report always returns Done.  Since when I use the message pop-up it returns DONE, I always filter out these steps from the report.

Hence I always include another Pass/Fail step with the Adapter as <None> immediately following the message popup.  The Pass/Fail criteria being something like 'RunState.PreviousStep.Result.ButtonHit == 1' .  This may not be an ideal situation since it would be necessary to add another step for each message popup.

Only other way I can think of changing the report format is modifying the 'ModifyReportEntry' callback.  In that callback, you would have to key off the 'MessagePopup' step type and make the modifications as needed.

PH

[StephenGerads]

I found that this works: 

in ProcessModelPostResultListEntry, add code to remove ButtonHit if present

Parameters.Result.DeleteSubProperty("ButtonHit",2) // 2 for delete if exists

[Sergey_Kolbunov]

For your step in the sequence open Step.Result in Variables pane, right click on ButtonHit, select Advanced>Edit Flags and uncheck "Include in Report" property. It is checked by default for custom step types created as combined types with the Message Popup general type.

That should be done for all instances of these step. When I tried just to incheck the "Include in Report" property in my step type, somehow it is still checked for all newly created steps of this step type. Possible solutions (besides changing them all manually as I described above) are to modify them at drop time from OnNewStep custom substep or to create automated script and run it on your sequences after creation to modify the flag.

Let me know if you need help with these solutions.

[StephenGerads]

Works great!

Based on that, I tried Pre-Expression: Step.Result.ButtonHit.SetFlags("",0,0) instead.

That works too.

Thanks for your help.

Regards,

Steve