Chrome tests are unstable about splinter HOT 10 CLOSED

Here at Nextown we had to work around a bunch of stuff in order to have some "stable" test lifecycle.

I'll share our workarounds in a gist, maybe you guys can take advantage of some code

from splinter.

Here we go

from splinter.

I have noticed another problem:

Apparently when I visit some page that has a iframe, for some reason webdriver* switches the content to the latest iframe

so when I test browser.url, it is pointing to the latest iframe, and I have to call browser.driver.switch_to_default_content() manually

* I've tested on chrome, but not in firefox

from splinter.

It seems that Chrome WebDriver it's not mature enough and it's the problem.

And my suggestion is to drop (for a while) Chrome support, by the following steps:

1. Freeze actual Chrome state (maybe in a branch)
2. Deprecate it in 0.0.4 release
3. Drop it in 0.0.5 release

I think we can provide support to Firefox on through WebDriver and focus on headless drivers (like PhantomJS and zombie.js).

What do you guys think? :)

from splinter.

I'd suggest you guys to use Semantic Versioning, http://semver.org/
why all the releases are only on patch level ?

And about chrome, here in Nextown webdriver-chrome is actually WAY more stable than webdriver-firefox, we are really hard users of splinter and we have so much to contribute (the problem now is basically time), so we have a lot more "patches" on webdriver, but we use them as mokey patches in our project.

I have already tried zombie.js for a particular purpose and trust me, both PhantomJS and zombie.js are unstable. Aditionaly, remember that headless drivers are not a silver bullet. They are awesome, dead fast, although they make SO hard to debug when a test fails, specially if the test failed due some UI/effects change with javascript.

Please consider supporting chrome, otherwise we will need to stop using splinter and apply our patches strictly to webdriver.

from splinter.

Ohh a note about Semantic Versioning:

The Semantic Versioning specification is authored by Tom Preston-Werner,
inventor of Gravatars and cofounder of GitHub.

from splinter.

Thanks for suggesting Semantic Versioning, we're going to check it :)

I talk to other repository collaborators and we decide to fork selenium and work on it, instead of drop Chrome support \o/

from splinter.

I'm -1 to drop chrome support, it is unstable but necessary.

About semantic versioning, we will think about it. :)

from splinter.

Sweet guys, thank you for ponderating on my points. I really appreciate.

from splinter.

Chrome tests are just VERY slow.

I'm closing this issue, because all we have to do is wait for Selenium guys :(

from splinter.