driver is incredibly slow about webdriverio HOT 9 CLOSED

I have not had the same experience with the slowness, but I agree that how the queue works and how exceptions are handled could be improved (e.g. using promises). If you do not supply a callback it does, in fact, just eat errors [1]

[1] https://github.com/camme/webdriverjs/blob/master/lib/utils/QueueItem.js#L56

from webdriverio.

Hi @delvarworld

sorry for my late response. I'm working on the error handling in webdriverjs. Do you have any suggestions for improvements?

I can't really imagine that webdriverjs is sooo slow. Actually it works like all the other libraries: sending JSONWire requests to a selenium server and operate with the response.

from webdriverio.

I don't have any suggestions, after switching to the main library I found no reason to switch back.

from webdriverio.

That's ok!

from webdriverio.

I also have this issue where WebdriverIO is slow. Gonna try to use the selenium lib, but just chiming in.

I am using Webdriver remote with SauceLabs, and doing waitFors. When looking at the SauceLabs screencast, the page is fully loaded, but the waitFor hangs doing nothing for 3 minutes even though the elements are there.

from webdriverio.

You don't need to use waitFor after opening an url. Selenium waits automatically until page is fully loaded. I haven't experienced a general slow experience at all using WebdriverIO.

from webdriverio.

It became perceivably faster once I called .screenshot() at the end? Maybe it was waiting for another command. My Sauce Labs tests went from 3min to 40sec about.

from webdriverio.

mhm interesting ... do you have an example script that can reproduce that?

from webdriverio.

Sorry for the slow response. I compared two webdriver clients where one ends with a .waitForExist and one ends with a .waitForExist + .screenshot. SauceLabs didn't consider .waitForExist a command and was waiting 90 seconds for more. Though I think that is expected so it's not actually an issue.

from webdriverio.