Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

deps(selenium-webdriver): upgrade to selenium 3 #3781

Merged
merged 18 commits into from
Dec 2, 2016

Conversation

cnishina
Copy link
Member

@cnishina cnishina commented Dec 1, 2016

No description provided.

- update to selenium-webdriver 3.0.1
- fix expected conditions test
- verify basic tests pass
using selenium standalon server 2.53.1

- upgrade to selenium-webdriver 3.0.x requires node version 6+, updating
  travis and circle yml to use node 6
- firefox 47 works
- selenium-webdriver/testing uses the global.it and cannot be
  reassigned as Protractor's global it. Required to copy some of their code
  to the lib/frameworks/mocha.js file
- WIP: still have tests that are not passing.

using selenium standalone server 3.0.x

- firefox 49 with gecko driver 0.11.1 does not work
- firefox 48 with gecko driver 0.11.1 appears to work for
  a single test but after it quits, selenium standalone
  no longer works with firefox.
- when firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```
- webdriver.quit throws a no session error
- define "quit" at runner.ts similar to restart where the driverprovider
  calls quit instead of the webdriver
- breakpoint updated to lib/http.js line 432
- removed method WebDriver.prototype.isElementPresent
- removed method WebElement.prototype.getRawId
- Chrome requires a ServiceBuilder and to call the Service to createSession
- Since this upgrade is still using FF 47, direct connect for Firefox
  is required to pass "marionette: false" in the capabilities. If you do not
  pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48 with direct connect and gecko driver.
@cnishina cnishina mentioned this pull request Dec 1, 2016
@@ -13,8 +13,8 @@ let logger = new Logger('element');

let WEB_ELEMENT_FUNCTIONS = [
'click', 'sendKeys', 'getTagName', 'getCssValue', 'getAttribute', 'getText', 'getSize',
'getLocation', 'isEnabled', 'isSelected', 'submit', 'clear', 'isDisplayed', 'getOuterHtml',
'getInnerHtml', 'getId', 'getRawId', 'serialize', 'takeScreenshot'
'getLocation', 'isEnabled', 'isSelected', 'submit', 'clear', 'isDisplayed', 'getId', 'getRawId',
Copy link
Member

Choose a reason for hiding this comment

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

we should remove getRawId too

Copy link
Member Author

Choose a reason for hiding this comment

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

done.

@@ -470,15 +470,13 @@ describe('ElementArrayFinder', function() {
browser.get('index.html#/form');
var labels = element.all(by.css('#animals ul li')).map(function(elm) {
return {
text: elm.getText(),
inner: elm.getInnerHtml()
text: elm.getText()
Copy link
Member

Choose a reason for hiding this comment

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

We should have something else here to make sure multiple promises are waited for. How about elm.getTagName?

Copy link
Member Author

Choose a reason for hiding this comment

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

Added elm.getTagName to the test.

for (var pos1 in WEBDRIVER.staticFunctions) {
var staticFunc = WEBDRIVER.staticFunctions[pos1];
it('should have a ' + staticFunc + ' function', function() {
it('should have static function', function() {
Copy link
Member

Choose a reason for hiding this comment

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

'should have static functions'? (and below)

@@ -42,7 +42,7 @@ describe('protractor library', function() {
browser.get('index.html').then(function() { finished = true; });
});

after('verify mocha waited', function() {
after(function() {
Copy link
Member

Choose a reason for hiding this comment

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

is this a change from Mocha? If not, we should continue to support a description for 'after' if it's a valid Mocha construct.

Copy link
Member Author

Choose a reason for hiding this comment

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

Added back after('verify mocha waited',

@juliemr
Copy link
Member

juliemr commented Dec 2, 2016

Please make sure that the description for the big commit links to the selenium-webdriver changelog: https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md

and gives a quick heads up about major breaking changes.

var SeleniumError = require('selenium-webdriver').error;
var Remote = require('selenium-webdriver/remote');
var Testing = require('selenium-webdriver/testing');

var WEBDRIVER = {
staticFunctions: ['attachToSession', 'createSession'],

instanceFunctions: ['actions', 'wait', 'sleep', 'getCurrentUrl', 'getTitle',
'takeScreenshot', 'getSession', 'getCapabilities', 'quit', 'touchActions',
Copy link
Member

Choose a reason for hiding this comment

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

Should we remove 'quit' from here then?

Copy link
Member

Choose a reason for hiding this comment

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

Nevermind, wrong place...

Copy link
Member Author

Choose a reason for hiding this comment

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

Looks like I got 'quit' to work.

Copy link
Member

Choose a reason for hiding this comment

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

Great!

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)
- Breaking changes including... (something here)
@cnishina cnishina merged commit 7b99045 into angular:beta Dec 2, 2016
@cnishina
Copy link
Member Author

cnishina commented Dec 2, 2016

Hooray! 😀 😊

cnishina added a commit to cnishina/protractor that referenced this pull request Dec 5, 2016
# Upgrade to selenium-webdriver 3.0.1

Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

### Removed methods

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

### Dependencies and versions

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

### Errors

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

### DriverProviders

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

### Managing Browser

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

### Debugging

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

### Mocha

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

### Setup Notes:

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```
cnishina added a commit that referenced this pull request Dec 8, 2016
# Upgrade to selenium-webdriver 3.0.1

Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

### Removed methods

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

### Dependencies and versions

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

### Errors

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

### DriverProviders

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

### Managing Browser

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

### Debugging

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

### Mocha

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

### Setup Notes:

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```
heathkit pushed a commit to heathkit/protractor that referenced this pull request Dec 15, 2016
# Upgrade to selenium-webdriver 3.0.1

Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

### Removed methods

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

### Dependencies and versions

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

### Errors

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

### DriverProviders

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

### Managing Browser

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

### Debugging

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

### Mocha

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

### Setup Notes:

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```
heathkit pushed a commit to heathkit/protractor that referenced this pull request Dec 19, 2016
# Upgrade to selenium-webdriver 3.0.1

Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

### Removed methods

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

### Dependencies and versions

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

### Errors

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

### DriverProviders

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

### Managing Browser

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

### Debugging

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

### Mocha

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

### Setup Notes:

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```
juliemr pushed a commit that referenced this pull request Dec 19, 2016
# Upgrade to selenium-webdriver 3.0.1

Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

### Removed methods

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

### Dependencies and versions

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

### Errors

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

### DriverProviders

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

### Managing Browser

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

### Debugging

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

### Mocha

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

### Setup Notes:

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```
juliemr pushed a commit that referenced this pull request Dec 20, 2016
Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```

To be squashed - fix up attach session typo
juliemr pushed a commit that referenced this pull request Dec 21, 2016
Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```

To be squashed - fix up attach session typo
juliemr pushed a commit that referenced this pull request Dec 22, 2016
Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```

To be squashed - fix up attach session typo
juliemr pushed a commit that referenced this pull request Dec 28, 2016
Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```

To be squashed - fix up attach session typo
juliemr pushed a commit to juliemr/protractor that referenced this pull request Dec 28, 2016
Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```

To be squashed - fix up attach session typo
sjelin pushed a commit that referenced this pull request Dec 28, 2016
Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```

To be squashed - fix up attach session typo
juliemr pushed a commit that referenced this pull request Dec 29, 2016
Note: with the upgrade, there might have breaking changes. Please see the selenium-webdriver changelog.

- See [selenium-webdriver changelog](https://github.com/SeleniumHQ/selenium/blob/master/javascript/node/selenium-webdriver/CHANGES.md)

- Removed method `WebDriver.prototype.isElementPresent`
- Removed method `WebElement.prototype.getRawId`
- Removed `getInnerHtml` and `getOutterHtml`

- Dependency required for upgrade: use `[email protected]`.
- Selenium-webdriver requires node version 6+, updating travis and circle yml to use node 6 and 7.

- Use `instanceof` selenium-webdriver error instead of error code. Selenium-webdriver error codes have been deprecated.

- Use executor with selenium-webdriver from `lib/http`. Deferred executor has been deprecated.
- Fix quitting `driverProviders`. When calling `webdriver.quit`, the control flow is shutdown and will throw an error.
- Driver provider for direct connect has been modified to use `ServiceBuilder` and to call the `Service` to `createSession`
- Note: Since this upgrade is still using FF 47, direct connect for Firefox is required to pass "marionette: false" in the capabilities. If you do not pass marionette to false, it will look for gecko driver in the PATH.
- Added a TODO to support FF after 48+ with direct connect and gecko driver.

- Updated `browser.manage().addCookie('testcookie', 'Jane-1234');` to use `browser.manage().addCookie({name:'testcookie', value: 'Jane-1234'});`

- Updated debug commons for breakpoint updated to selenium-webdriver `lib/http` line 432.
- Debugger currently does not work. So `elementExplorer` for this current commit does not work. Additional work is required.
- Since debugger does not work, interactive tests were disabled in `scripts/tests.js`

- For mocha tests, `selenium-webdriver/testing` uses the global `it` and cannot be reassigned as Protractor's global `it`. Some code has been copied / modified to `lib/frameworks/mocha` to make this work.

- Capabilities for Firefox 47 requires setting marionette to false.
- Setup still requires selenium standalone server 2.53.1 for Firefox tests. Firefox version used is 47.
- Using selenium standalone server 3, with Firefox 48+ tests fail with gecko driver still do not work.
- Selenium standalone 3 + FF 49 + gecko driver 0.11.1 does not work
- Selenium standalone 3 + FF 48 + gecko driver 0.11.1 appears to work for a single test but after it quits, selenium standalone no longer works with firefox. When firefox 48 exists, logs show the following:

    ```
    20:01:14.814 INFO - Executing: [delete session: e353fa1b-e266-4ec3-afb3-88f11a82473a])
    [GFX1-]: Receive IPC close with reason=AbnormalShutdown
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    [Child 30665] ###!!! ABORT: Aborting on channel error.: file /builds/slave/m-rel-m64-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp, line 2052
    ```

To be squashed - fix up attach session typo
@cnishina cnishina deleted the selenium3 branch November 5, 2018 17:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants