Has anyone been successful controlling a BIRT Report window with QA Wizard scripts?
There is an html element on the BIRT Report View window that when viewed thru IE 6 (IE 6 is a requirement of my application) and is clicked on it generates a new window and the user can select the type of export they want (excel, word, etc.). The html element is exportReport. Within my recorded script, the html element cannot be found…
Sample script is below…
Window("window").Button("Run This Report").Click()
'the run this report button causes a BIRT window to be generated and the report runs successfully..
Window("BIRT Report Viewer").HTMLElement("exportReport").WaitForLoad()
The error message generated is below…
The control exportReport cannot be located or did not load. Searched for 120 seconds.
And I assume that the report does really run? Is "exportReport" the actual window control? Is there an object on that window that you can memorize with Checkpoint? You could tick the "Check Exists" option on the Checkpoint screen and if the normal "WaitForLoad", "WaitForLoadTimed", "WaitForExists" or "WaitForExistsTimed do not work maybe you could try a do/while loop around the "Check Exists" function to search for it. These are just ideas, I can't speak for BIRT but we have a similar window which is difficult to validate and it performs a similar function
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~
I had identified myself as new to QA Wizard scripting..so you will see... I found out what is causing the problem. BIRT is generating a tempary (I believe) URL for each report (or each set of parameters requsted) that is generated. I beleive that QA Wizard is trying to match on the entire URL to determine that it has the correct BIRT Report Viewing window...
I had been recording with QAW one report and trying to match a new report .... The two urls are different.
So now I do not know how going to get the script to execute.. [img]/images/graemlins/confused.gif[/img]