I change it to 15000 but no change seem so.
I will replace the ClickItem function by Click.
Thanks for your investigation.
gbraillon wrote:
There is the firefox icon because when i created the keyword test i used firefox at first, but now i use IE in both environement (local & VM).
No call to firefox in my scripts.
If you don't find, i will have to transform all my clickItem in Click. Example: linkManage.ClickItem("Users") to linkManage.Click; linkUsers.Click;
It seem it work this way.
That clues me in to it being a timing issue in there as well... you mention that your global auto-wait timeout is already 13 seconds... funnily enough, if you look at the time stamp on your TestExecute log, it is exactly 13 seconds after the last log entry that the error occurs.
Try increasing the Auto-Wait Timeout on your specific operation (right click on the operation, select "Set Auto-Wait Timeout for Operations", turn off the option to use the default, and bump your timing up to a higher value). If your TestExecute environment is a VM with less resources, it's entirely likely that it could take a while for certain things to be recognized.
Which, again, is an environmental issue... the environment of your TC machine is different than your TE machine... your automation needs to take this into account.
I change it to 15000 but no change seem so.
I will replace the ClickItem function by Click.
Thanks for your investigation.
Upping from 13 seconds to 15 seconds really isn't a significant change to see whether or not that is the problem. I'd bump the timing of the operation all the way up to 60000. This does not mean it will wait 60 seconds, but that it will wait UP TO 60 seconds... if this doesn't fix it, then there's something else going on.
Again... you have environmental differences that need resolved.
Yes it seem there is performance issue on VM.
Thanks, i will investigate.
