-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI setup should be improved to test on Selenium 3 #257
Comments
We can Safari tests, but last time I've checked they weren't passing at 100%. Mostly due bugs in SafariDriver side. |
Why not. Some people might still be using Selenium 2 with Chrome. |
This is an idea, if the Travis OSX environment allows to run Safari (the Travis doc does not say anything about this). But it would be hard to fix them as I have no way to run Safari.
The Selenium SafariDriver is totally unmaintained (last release was with Selenium 2.48, and was already missing features compared to other drivers). And I have not found anything about the new Apple SafariDriver except the announcement blog post saying it comes pre-installed with Safari 10+, so I don't know whether it works fine or no (but being the first release of the driver, it may well be buggy and incomplete) and I don't know whether they followed the Selenium driver spec or the W3C draft (in which case, it would be bad if they don't update the driver more often than OS X releases, given that the W3C spec has many changes since August) |
Hello, What I should expect when I try to run selenium2Driver (through Behat 3.x), Selenium 3.5.x, and Firefox 56.x? I have done few tests so far, and even basic functions (filling the search field in google page i.e.) does not seem to work (working fine with chrome BTW). Thanks for your feedback, Tony |
I plan to add 2 more jobs in the matrix:
I'm wondering whether we should also add Selenium 2 + ChromeDriver in the matrix. not sure it is worth it.
refs #254
The text was updated successfully, but these errors were encountered: