UFT11.51 Sync method doesn't seem to be using Browser Navigation Timeout
In our QTP tests we used an increased Browser Navigation Timeout to accomodate pages that were slow to appear.
So when we used Browser().Sync or Browser().Page().Sync QTP seemed to use a combination of Browser Navigation Timeout and Object Synchronisation Timeout to calculate the total time to wait.
In UFT these tests now fail because UFT appears to only use the Object Synchronisation Timeout.
Does this make sense and has anyone experienced anything like this?
QTP is quite good when it comes to basic sync but things get complex when AJAX components come into play. I recommmend you to use a combination fo checking the object's visibility/display along with the .Exist method to really know if the page has completely loaded. An example here: http://relevantcodes.com/qtp-synchronization-for-ajax-applications/
I'm not asking for advice on how to perform synchronisation in our scripts - we know how to do that and we already do it in countless situations.
What I'm reporting is the fact that on our systems UFT 11.51 behaves differently from QTP 11 in that it doesn't appear to use the Browser Navigation Timeout after sync calls. This seems to us to be a fundamental aspect of QTP/UFT script playback and I'm surprised no one else has seen this behaviour. I'll raise a support call with HP.