search

Zarkonnen / se-interpreter

Interpreter for Selenium Builder JSON scripts based on node.js and wd.
34 stars 31 forks source link

SeInterpreter not working when using FF26 to run tests. #7

Closed bowlej closed 10 years ago

bowlej commented 10 years ago

I am seeing an issue with SeInterpreter and FF26 . I will try and grab some logs if that would help. Dropping back to FF 25 has allowed me to keep running my tests.

bowlej commented 10 years ago

Some logging:

JavaScript error: chrome://browser/content/urlbarBindings.xml, line 654: aUrl is undefined

at org.openqa.selenium.firefox.internal.NewProfileExtensionConnection.start(NewProfileExtensionConnection.java:106)
at org.openqa.selenium.firefox.FirefoxDriver.startClient(FirefoxDriver.java:251)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:110)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:197)
at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:190)
at com.sebuilder.interpreter.webdriverfactory.Firefox.make(Firefox.java:47)
at com.sebuilder.interpreter.TestRun.next(TestRun.java:77)
at com.sebuilder.interpreter.TestRun.finish(TestRun.java:127)
at com.sebuilder.interpreter.Script.run(Script.java:68)
at com.sebuilder.interpreter.SeInterpreter.main(SeInterpreter.java:98)

Dec 23, 2013 5:14:22 PM com.sebuilder.interpreter.SeInterpreter main INFO: Tests/full_example.json failed java.lang.RuntimeException: Test run failed: unable to create driver. at com.sebuilder.interpreter.TestRun.next(TestRun.java:79) at com.sebuilder.interpreter.TestRun.finish(TestRun.java:127) at com.sebuilder.interpreter.Script.run(Script.java:68) at com.sebuilder.interpreter.SeInterpreter.main(SeInterpreter.java:98) Caused by: org.openqa.selenium.WebDriverException: Failed to connect to binary FirefoxBinary(/Applications/Firefox.app/Contents/MacOS/firefox-bin) on port 7055

bowlej commented 10 years ago

Dropping back to FF 25 allows me to continue to run tests.

My version of OSX is:

OS X 10.9.1 (13B42)

bowlej commented 10 years ago

Looks like its related to this issue:

https://code.google.com/p/selenium/issues/detail?id=6517

Once i swapped in the latest selenium jar (selenium-java-2.39.0) and renamed it to match the version package with se-interpreter (selenium-java-2.35.0) it worked fine with FF26