Posts: 25
Threads: 11
Joined: Jan 2008
Reputation:
0
07-02-2008, 09:49 PM
Hi everybody!
I recently upgraded to QTP 9.5 and and important regression script (apart from other stuff) stopped working because it used the
Browser(<name>).Navigate(<url>)
function.
The call of this function NOW HAS NO EFFECT WHATSOEVER! I did not find any help in the net or in the application, I dont even know if Mercury give out release notes.
So - if there is any way of archiving this functionality or fixing the QTP bug - pleease let me know!
Thanks very very much!
CC
Posts: 38
Threads: 4
Joined: Jul 2008
Reputation:
0
07-03-2008, 02:23 PM
Try using a exist function that QTP recognises the browser first and then do a object spy on the browser to check for the navigate method.
Posts: 25
Threads: 11
Joined: Jan 2008
Reputation:
0
07-03-2008, 09:20 PM
Hi Nageshpv!
Thanks - but of course the Browser exists (exist(n) returns true), and so does the Navigate method. It still takes one mandatory parameter (the url), so actually nothing has changed since the last version of QTP, but still it does not work in the new version.
Anyone here who uses 9.5 and "Browser(..).navigate(..)" and where it actually works? Then at least I would know that there must be a way to get it done, as opposed to assuming that the HP guys just didnt get it right here...(as seen in other places of QTP)..
THANKS!!!!
CC
Posts: 25
Threads: 11
Joined: Jan 2008
Reputation:
0
08-20-2008, 04:56 PM
Hi again!
(yes, sorry, this is a bump)
Thanks all!
But I am still looking for answers on this one, as my workaround ("manually" enter the url into the browser-url-text-box and then click the "go" button) is not very cool.
I was hoping that after some updates of QTP this will be fixed. But it is not. Not with my settings at least.
Anyone any answers, or a Mercury contact for complaints? (We signed up for support here ages ago, and just did not get an answer).
Thanks!
CC