Recently, I got my machine replaced and I had to start installing stuffs all over again. I have 64-bit Windows machine and instead of using 64-bit IE driver, I used 32-bit IE driver. The reason for using the 32-bit IE driver is obviously the slow typing issue in 64-bit one, and switching seems the only option as can be found in below threads.
Why is Selenium InternetExplorerDriver Webdriver very slow in debug mode (visual studio 2010 and IE9), and WebDriver and IE10 very slow input
My questions are:
Can slow typing issue be solved without really switching to 32-bit IE Driver?
What is the need of 64-bit IE driver when it can slow down your tests very much?
On Selenium official download page, 32-bit is recommended, do we actually require 64-bit.
As pointed out in the link shared by @Saifur above, there seems to be the workaround for using 64-bit instead of switching to 32-bit(though I haven't yet tested it and probably never will).
First, you can disable native events by setting the "nativeEvents" capability to false using whatever mechanism your language binding provides for this.
and,
A more accurate workaround from an input simulation perspective would be to enable the "requireWindowFocus" capability, though this also has a windows hook dependency, which may manifest in other ways.
Can slow typing issue be solved without really switching to 32-bit IE Driver?
To my knowledge no. I did a benchmarking on login page of my application using 32x vs 64x version. There are significant amount of performance improvement when you use 32x as you know.
What is the need of 64-bit IE driver when it can slow down your tests very much?
Couple of reasons why.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With