| || |
Sync is not working in UFT
I am facing sync issue with UFT 11.53. Previously we have developed scripts in QTP 11, Now all the machines got migrated to UFT 11.53. The whole scripts are getting failed in UFT 11.53 which were successfully passed in QTP 11. I tried enabling BHOManager as well, but no luck.
Below statements are taking zero seconds to execute.
Please suggest me on this.
Have You checked the Object Synchronization Timeout setting is as you expect it:
Settings > Run
Yes. All the settings are set to default ones. And one more thing want to add, we are working on BPT(Business Process Testing).
Are the objects in the OR unique from each other (use different property values)? If not, syncing will not matter.
Maybe try: "Add X seconds to page load time" in the Options>Web>
There is alos n "Ignore ALM/QC" checkbox there. Not sure if unchecking it will help, but maybe that makes a difference since you are using BPT (with QC).
Note - these are the QTP not UFT settings, so not sure if UFT is the same.
1 more thing....Maybe QTP used seconds and UFT uses milliseconds. so 60 seconds is now .06 in uFT I remember either WinRunner or QTP (AstraQuickTest?) changed like this years ago between versions. Check the Help documents.
I wonder if an error is occurring. Maybe keep an eye on err.description after the sync.
When we moved to UFT we noticed that Browser().Page().Sync didn't seem to use the Browser Navigation Timeout setting as expected, but Browser().Sync was OK. We raised the following call with HP, which is still 'under investigation'. We solved our problem by replacing all BRowser().Page().Sync's with Browser().Sync.
In QTP 11, both Browser().Sync and Browser().Page().Sync statements correctly use the Browser Navigation Timeout (default to 60 secs) to wait for pages to load. Customer relies upon this timeout to synchronise slow operations in their application.
In UFT 11.51, Browser.Sync has the same behaviour as in QTP 11 (uses the Browser Navigation Timeout as timeout value for the Sync method). However, Browser().Page().Sync uses the Object Synchronisation Timeout instead as timeout value.
Replacing Browser().Page().Sync by Browser().Sync
Internal Change Request
Internal Legacy ID:
I sometimes was able to communicate better with WebTables when I left out the page level of identification. This was in QTP 10 and 11.
So you were using a
Kind of approach Kevin?
When do you expect to get back to QTP automation Kevin?
I don't understand your question about getting back to QTP automation.