UFT 12.01 issue with webedit on FireFox and Chrome
I am using UFT 12.01, I am facing issues with webedit on Firefox and Chrome, Its taking almost 1 minute to fill the edit box.
It is working perfectly fine on Internet Explorer. I installed UFT extensions on firefox and chrome.
I am using FireFox 28.0 and Chrome 39
Please suggest me if I have to update anything.
Wow! The FF and Chrome version numbers keep increasing.
HP must have a full time person just trying to keep up with the latest release.
I have not worked with these versions yet.
It is one way of FF and Chrome developers saying "You create a tool which supports IE out-of-box, we'll make you suffer with our weekly or bi-weekly releases of newer FF and Chrome versions. Happy now HP?"
Originally Posted by bklabel1
What value do you have set in the "Object Sync Timeout" setting, try reducing it to a small value like 4 seconds.
Always check the PAM pdf document that comes with each UFT version.
Originally Posted by ppradeepqa
In there, you'll see that UFT 12.01 supports Firefox up to version 31 and Chrome up to version 36.
In short, UFT 12.01 should work with Firefox 28 but not with Chrome 39.
What optimization steps have you taken?
What I suspect is since Firefox and Chrome support shadow dom. You could have a situation that the automation tool is indexing a lot of off screen elements. Depending on the complexity of the controls, or how much customization. There could be essentially a large index tree.
First You want to do the following..
1. monitor the memory, CPU cycle, and disk activity. Make sure you're not exhausting your system resources.
2. Add timers and calculate the time it takes for:
a) object aquisition.
b) performing the action.
c) if there are parent objects, you might want to do some experiments on the time it takes to acquire some of the parent objects.
This will allow you to isolate the problem and help you debug. You can make optimizations in how objects are found if that's the slow part. If the performing the action is slow, then you want to see if there are optimizations such as caching and reference reuse the object reference if the action involve multiple steps. If several objects share the same parent, caching on the parent object level, then doing shallower finds on the child objects will help. Other things you can do to speed up things relating to actions is find alternatives. For example, instead of Send keys to a text field, it's generally faster to set them in memory using their value hooks.
3. Add some performance monitoring of the page itself such as gomez, Gomez | Compuware, so you can figure out if it's the test running slow, or is it the page that's running slow.
I agree with mwsrosso that you should try to change the time out setting from 60 seconds to 1-2 seconds. Also, please check in your test result whether the object has been identified by smart identification or not? I suspect UFT takes time to set a value into edit box because the object cannot be found with object properties in your repositories.
Please check supported chrome and firefox versions in UFT help
Change the object time out setting to 5 seconds