+- Micro Focus QTP (UFT) Forums (https://www.learnqtp.com/forums)
+-- Forum: Micro Focus UFT (earlier known as QTP) (https://www.learnqtp.com/forums/Forum-Micro-Focus-UFT-earlier-known-as-QTP)
+--- Forum: UFT / QTP Beginners (https://www.learnqtp.com/forums/Forum-UFT-QTP-Beginners)
+--- Thread: QTP is identifying Browswer as a Window (/Thread-QTP-is-identifying-Browswer-as-a-Window)
QTP is identifying Browswer as a Window - Debby Browne - 05-12-2011
When we run our existing QTP 10 tests on a new 64-bit Windows 7 machine, the web browser we are testing is identified as a Window instead of a Browser (even though we start IE in 32-bit mode), so no objects are identified and the tests fail completely. We have another Windows 7 machine that has no problem identifying the Browser, but it is a 32-bit machine. Or is the 64/32-bit issue a red herring, and the problem related to some QTP setting that I'm missing?
Thanks in advance for any reponses!
RE: QTP is identifying Browswer as a Window - sreekanth chilam - 05-12-2011
Hi,
Have you opened the Browser first and then QTP?
If so open the QTP first > open Browser > Identify the Brower
RE: QTP is identifying Browswer as a Window - Debby Browne - 05-13-2011
No, I open QTP first, and then the browser - and QTP sees the browser as a Window class.
FYI, the machine in question has these patches: QTP_00626, QTP_00644, QTP_00684 and QTPNet_00046 (for testing our Silverlight controls). The QTP_00644 patch is specifically for supporting Windows 7.
Before I installed those patches, the OS environment variable was empty and it now has "Microsoft Windows 7" as the OS. But we're still missing something, as IE8 is not being recognized as a Browser. Any ideas?
Debby
RE: QTP is identifying Browswer as a Window - supputuri - 05-13-2011
Try running the QTP and browser as admin.
RE: QTP is identifying Browswer as a Window - Debby Browne - 05-13-2011
Thanks so much for your response!
Well unfortunately that works! Just opening QTP as admin (and having QTP open the browser) was not enough - I also had to manually open the browser as admin too.
I say unfortunately because we HAVE to be able to open our browser directly from QTP, which we have up to now been doing using the SystemUtil.Run method, because we have to enter credentials (UserName/Password) automatically from parameters that are passed to the test. (We force the credentials challenge by setting our local Intranet Options, Security settings to custom--> prompt for user name and password). We need to do this because different users have different permissions and a large part of our testing is making sure the appropriate users can only see the records that they own.
SOoooo....do you know of a way to open a browser "As Admin" directly from QTP?
We have no problem testing as described above, on Windows XP and we also had no problem even on our 32-bit Windows 7 machine - UNTIL TODAY. BUT TODAY (or perhaps last night), something changed on that Windows 7 machine so that now it too can't recognize the browser for our existing tests - QTP thinks the browser is a window class.....the same as it has been doing for our new (64-bit) Windows machine. This is just too confusing.
But at least if we had a way to open a browser as admin directly from QTP, or if there is some other workaround for this problem, we could proceed. Any ideas on this?
Debby
RE: QTP is identifying Browswer as a Window - amitv - 05-13-2011
Have you checked the Web Add in?
Try after selecting it at startup.
-Amit
RE: QTP is identifying Browswer as a Window - atanu - 05-13-2011
Hi ,
Disable UAC setting if enabled on Windows7.
Try it and see if that helps.
Atanu