Open chapulina opened 8 years ago
@ryantmer, thanks for referencing the issue. Adding "wct-local": "2.0.12"
as a dev dependency also solves the issue for us - for chrome. Firefox 49 still doesn't work, but it used to.
wct-local 2.0.12 also overrides the firefox driver version to 0.11.1 (if not overriden it will be 0.10.0)
"selenium-overrides": { "drivers": { "firefox": { "version": "0.11.1"
+1 We're also seeing this and are looking for a fix. wct-local didn't fix it for us :(
The same problem rises when you create a component with polymer CLI polymer init
(element - A blank element template) and right after that run polymer test
.
(MacOS Sierra with java version "1.7.0_71", node v7.0.0, polymer-cli 0.17.0)
Looks like we really need configuration (#403) for selenium to have control over its installation and fixing its own problems not related to wct.
Update: upgrade to Java 8 fixed this problem, but Safari still doesn't work.
So, intrigued by the fact that the Google team can still work on the paper elements in their Travis CI server (e.g. https://travis-ci.org/PolymerElements/paper-input/jobs/172163606). I decided to replicate the environment in my Docker container:
And all works fine. But had the same error with the default Java 7.
Thanks a lot that solved my problem!
@bashmish I used selenium-server-standalone-2.45.0.jar for safari, thats the most recent version that works for me, for others browsers, I can used latest, right now using selenium-server-standalone-3.0.1.jar, on java8, and just calling -Dwebdriver.chrome.driver in this order: java -jar -Dwebdriver.gecko.driver=geckodriver.exe selenium-server-standalone-3.0.0-beta2.jar
@joaovieira - can you please post your Dockerfile? I am trying to create a Docker container for WCT and running into problems.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
At some point yesterday all our tests started failing because of the Java version:
On another computer, we upgraded the Java version to 8 and now the tests pass for Chrome 56, but there are new errors for Firefox 49. It would be great to go back to using an earlier Java version.
I'm not sure if the problem was caused by some change in wct or if it comes from upstream. Please close this issue if the problem wasn't introduced here, and in that case, it would be great if you could point me to whom I should be bugging instead.
Thanks!