Skip to content
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

Travis: Make Selenium use Marionette instead of the add-on based driver #489

Merged
merged 8 commits into from
May 26, 2016
Merged

Travis: Make Selenium use Marionette instead of the add-on based driver #489

merged 8 commits into from
May 26, 2016

Conversation

JohanLorenzo
Copy link
Contributor

@JohanLorenzo JohanLorenzo commented May 19, 2016

The current beta version of Firefox break the Selenium tests. This can be reproducible locally. It'll impact our tests once 47 reaches release.

From the Selenium server logs, the installation of the addon in Firefox is not supported anymore. The fix is to make Selenium plug into Marionette server.

@JohanLorenzo JohanLorenzo changed the title [Do not merge] check if firefox beta is broken on Travis Travis: Make Selenium use Marionette instead of the add-on based driver May 19, 2016
@@ -38,7 +38,7 @@
"node-ssdp": "^2.7.0",
"path": "^0.12.7",
"raw-body": "^2.1.6",
"selenium-webdriver": "2.53.1",
"selenium-webdriver": "https://github.com/JohanLorenzo/selenium/releases/download/2.54.0-dev/selenium-webdriver-2.54.0-dev.tgz",
Copy link
Contributor Author

@JohanLorenzo JohanLorenzo May 23, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wish I could add a comment, but JSON doesn't allow it. This is a workaround until SeleniumHQ/selenium#2137 lands in master and a new version is released on npm (likely 2.54)

@coveralls
Copy link

Coverage Status

Coverage increased (+0.7%) to 37.615% when pulling 10c0313 on JohanLorenzo:check-firefox-beta into 19bb815 on fxbox:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.7%) to 37.615% when pulling 10c0313 on JohanLorenzo:check-firefox-beta into 19bb815 on fxbox:master.

capabilities.set('marionette', true);
const driverBuilder = new webdriver.Builder().withCapabilities(capabilities);

console.log(driverBuilder.getCapabilities());
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Remove this line

@JohanLorenzo
Copy link
Contributor Author

Build against Firefox 47 is green. So is Firefox 46 (that version supports both Marionette and the add-on driver).

r? @npark-mozilla

@nojunpark
Copy link

looks good to me, hopefully when this is merged, it's still working for me locally as well. r+

@nojunpark
Copy link

nojunpark commented May 24, 2016

Actually, I rolled back my rust and ran this, and got following error on the first time I ran it, but the test is consistently passing after that, if this is caused by my setup, please ignore.

  1. Test set up UI sessions ui once registred signin page should reject not matching passwords:
    WebDriverError: can't convert null to object
    at WebDriverError (node_modules/selenium-webdriver/lib/error.js:27:10)
    at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:611:11)
    at parseHttpResponse (node_modules/selenium-webdriver/http/index.js:518:15)
    at node_modules/selenium-webdriver/http/index.js:466:11
    at ManagedPromise.invokeCallback_ (node_modules/selenium-webdriver/lib/promise.js:1343:14)
    at TaskQueue.execute_ (node_modules/selenium-webdriver/lib/promise.js:2868:14)
    at TaskQueue.executeNext_ (node_modules/selenium-webdriver/lib/promise.js:2851:21)
    at node_modules/selenium-webdriver/lib/promise.js:2775:25
    at node_modules/selenium-webdriver/lib/promise.js:639:7
    From: Task: WebDriver.switchTo().alert()
    at Driver.schedule (node_modules/selenium-webdriver/lib/webdriver.js:386:17)
    at TargetLocator.alert (node_modules/selenium-webdriver/lib/webdriver.js:1591:29)
    at node_modules/selenium-webdriver/lib/until.js:117:30
    at node_modules/selenium-webdriver/lib/webdriver.js:718:14
    at TaskQueue.execute_ (node_modules/selenium-webdriver/lib/promise.js:2868:14)
    at TaskQueue.executeNext_ (node_modules/selenium-webdriver/lib/promise.js:2851:21)
    at node_modules/selenium-webdriver/lib/promise.js:2775:25
    at node_modules/selenium-webdriver/lib/promise.js:639:7
    From: Task:
    at pollCondition (node_modules/selenium-webdriver/lib/promise.js:2314:16)
    at node_modules/selenium-webdriver/lib/promise.js:2310:9
    at new ManagedPromise (node_modules/selenium-webdriver/lib/promise.js:1048:7)
    at node_modules/selenium-webdriver/lib/promise.js:2309:14
    at TaskQueue.execute_ (node_modules/selenium-webdriver/lib/promise.js:2868:14)
    at TaskQueue.executeNext_ (node_modules/selenium-webdriver/lib/promise.js:2851:21)
    at node_modules/selenium-webdriver/lib/promise.js:2775:25
    at node_modules/selenium-webdriver/lib/promise.js:639:7
    From: Task: Waiting for alert to be present
    at ControlFlow.wait (node_modules/selenium-webdriver/lib/promise.js:2307:17)
    at Driver.wait (node_modules/selenium-webdriver/lib/webdriver.js:714:29)
    at Object.waitForAlert (test/selenium/lib/view/alert.js:19:24)
    at Object.message (test/selenium/lib/view/alert.js:11:17)
    at test/selenium/lib/view/sign_in/view.js:25:39
    at ManagedPromise.invokeCallback
    (node_modules/selenium-webdriver/lib/promise.js:1343:14)
    at TaskQueue.execute_ (node_modules/selenium-webdriver/lib/promise.js:2868:14)
    at TaskQueue.executeNext_ (node_modules/selenium-webdriver/lib/promise.js:2851:21)
    at node_modules/selenium-webdriver/lib/promise.js:2730:27
    at node_modules/selenium-webdriver/lib/promise.js:639:7

@JohanLorenzo
Copy link
Contributor Author

JohanLorenzo commented May 25, 2016

@npark-mozilla This error should have been worked around by this selenium client. Does the error occur after npm install? If so, I don't think I fixed the root cause of it 😨

Edit: I just pushed an unbitrot revision. Nothing related to that particular failure

@coveralls
Copy link

coveralls commented May 25, 2016

Coverage Status

Coverage remained the same at 37.616% when pulling 3527b9e on JohanLorenzo:check-firefox-beta into fe8f66f on fxbox:master.

@nojunpark
Copy link

nojunpark commented May 25, 2016

We could merge this, right?

EDIT: or right, r+. I think above error was caused by me not running npm install beforehand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants