| || |
Using QTP to automate FF browser
I have several questions in regards of using QTP. We usually face many QTP issues while we are working on our automation. I mentioned some of them below.
1. Supporting FF browser
Our automation should support both IE and FF browsers. In regards of FF, the QTP tool doesn’t click on buttons / links properly in this browser. One of the common issues is that I am not redirected (usually) to another page after I click on the button / link. Sometimes, I can see really weird behavior upon clicking on the link / button. For instance, the page is reloaded and so on.
Usually I have to use the ReplayType = 2 in order to move to another page successfully. Apparently, I should use the ReplayType = 2 whenever I want to run my automation against FF browser.
There is another issue when I use the ReplayType = 2 in FF. Upon clicking on the link / button, I will be redirected to right page. However, QTP fails due to the new page is not recognized. We store our objects in Object Repository. When I use attempt to recognize the same page from the repository, it works well. I fixed this issue by adding Wait statement in my script. Upon clicking on the link / button, I wait about 3 seconds. Then I am able to recognize the new page successfully.
When I use ReplayType = 1, I don’t need to wait. However, as I mentioned above, using ReplayType = 1 is not reliable in FF browser.
Please, do you use QTP for running automation against FF browser? If you run your automation, do you usually use browser events or mouse?
2. Cannot click on OK / Cancel button in standard dialog window in FF
Another issue relates to the dialog windows in FF browser. When I attempt to close a confirmation dialog in FF, QTP usually fails. QTP recognizes the dialog window correctly. However, QTP doesn’t recognize any WinButton object displaying in the dialog. I have to use the Sendkeys() method which is included in “WScript.Shell” object. Does anyone have the same troubles? If so, what solution do you use to come around this issue?
Note: When I run my script against IE browser, QTP recognizes the WinButton objects properly.
Sometimes I have to parse HTML source code in order to retrieve current values. I usually use the “InnerHTML” property. This property is supported by both IE and FF browsers. Well, each browser supports this property in different way. QTP returns completely different outcomes for both browsers. What makes me feel upset is that QTP returns wrong outcome for FF browser. Sometimes I cannot see the end HTML tags. When I view the source code in notepad, everything looks all right. When I use the InnerHTML property to retrieve the source code, QTP usually omits some end HTML tags in FF browser. Thus I have to implement a lot of conditions in my script. Does anyone encounter similar issue?
As far as I am experienced, it seems to me that using QTP to automate FF is not good idea… It usually takes me a lot of time to tune my automation to support FF browser. Sometimes it is faster to develop whole automation using IE browser then to update the same script to support FF browser.
I would appreciate all your opinions [img]/images/graemlins/smile.gif[/img]
Re: Using QTP to automate FF browser
Sigh... Search this forum before posting what you believe is a "new" question.
Problems and issues with using FireFox have been discussed many, many times. Here is but one (of hundreds) of posting that you find using the Advance search button at the top right hand corner of this page: