AutoitX not working, Trend and possible alternatives?

[frankh]

Tried it. No change.

[Earthshine]

So sorry,

I found this, it helps WebDriver, which Selenium uses, to drive Chromium. I hope you can speed things up with that. Also, do you think that changes in your network environment have caused this behavior?

http://www.automationtestinghub.com/selenium-chromedriver/

Edited March 27, 2018 by Earthshine

[frankh]

The network environment cannot have anything to do with it. The delay is with SendKeys() and equivalent actions accessing a local form. Also, I've been trying all variants of the chromedriver, with no different results. Remember: This suddenly happende with code - both uncompiled and a built and compiled application - that had not been changed in any way. So the change is somewhere in Windows.

Edited April 3, 2018 by frankh

[Earthshine]

yes, the change is in windows. if you are in a large, networked professional environment, it is not uncommon for group policy changes and other updates/changes to get installed or applied. Do you have a system restore point old enough to revert to to try? Would you even want to do that (rather heavy handed and IT probably won't like it)

PS, this is why I do all testing on static VMs that can be rolled back to a good snapshot. Sorry. But, you have now something you can go to your Network/IT guys with asking for help with?

Edited April 3, 2018 by Earthshine

[Earthshine]

Just looked at Stack Overflow

https://stackoverflow.com/questions/25240002/automation-execution-is-too-slow-in-chrome-using-selenium-webdriver-36

Perhaps try using a 32 bit version of Chrome?

Quote

1down vote

The answer can be the following if you use 64-bit OS architecture on your PC - as far as I remember is because Selenium performs switching between 32-bit and 64-bit mode (which is very slow operation). ChromeDriver was supported only in 32-bit. I had same issues with IE driver too.

Update:

Next thing to check then is that the proxy and network settings in chrome have not been altered. In the begging I considered extensions and add-ons, but Selenium raises clean instance each time. As to #36 being slow - check the dev threads on google chrome, you will see the issue has been ongoing for well over 6mths and is affecting cross-platforms too. And one solution is try disabling hardware acceleration.... it was a tenfold improvement for me on my laptop. To disable it... type "chrome:settings" in the address bar, click Advanced Settings, then uncheck "Use hardware acceleration when available" under the System header. Close all open Chrome browser instances and restart Chrome.

I hope you snapshotted the good VM, and when you roll back, note which version of chrome you are using.

Edited April 3, 2018 by Earthshine

[Earthshine]

snip

i was wondering what version of Node you have installed as well. And as an alternative that still uses AutoIt, you could try IUIAutomation by @junkew

 

Using his simplespy.au3 get the data from that form and see if we can login not using slow selenium drivers. I can help you if you want to try.

 

 

Edited April 3, 2018 by Earthshine