Tests run much slower on the Chrome browser than on Firefox.
In Chrome, WebDriver uses only about 20-30% CPU and, looking at it, seems to frequently
sleep for a fraction of a second. It thus takes more than twice as much time as Firefox
for the same test suite.
I'm running Selenium 2 through Ruby's selenium-webdriver (0.1.3.dev) and capybara (edge)
on Linux/tightvncserver. Inside the remote-controlled Chrome browser, it says WebDriver
extension version 1.9.17.
(This also happened with the previous version of the selenium-webdriver Ruby gem, so
it doesn't seem to be a new bug.)
Does this only happen on my system, or can other people reproduce it?
If this is not just my setup having a problem, then I'll mention that IMVHO it's really
a shame that the Chrome driver is so slow. Chrome feels very fast on my desktop, so
I'd expect it to be the platform of choice for running browser tests. I've also documented
this here, by the way:
Reported by joliss42 on 2011-02-13 02:07:48
The text was updated successfully, but these errors were encountered:
The Chrome driver is in the process of being rewritten as part of the Chromium tree:
We won't prioritize working on the performance of the current driver. If you want to
dig in and create a patch, I'd be happy to merge it though.