-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Update to WebDriver 2.47.1 #2245
Comments
I would appreciate if you could add the proxy support to Protractor that comes with WebDriver 2.46 as well. DriverProvider.prototype.getNewDriver = function() {
// ...
usingWebDriverProxy(this.config_.seleniumProxy).
// ...
} |
See also #2263 |
Here's a test which hangs with webdriver 46, but not 45. var webdriver = require('selenium-webdriver');
var driver = new webdriver.Builder().
usingServer('http://localhost:4444/wd/hub').
withCapabilities(webdriver.Capabilities.chrome()).
build();
var flow = webdriver.promise.controlFlow();
driver.get('http://www.w3schools.com/html/html_lists.asp');
var printTexts = function(webElems) {
var attrVals = webElems.then(function(arr) {
var results = arr.map(function(webElem) {
return webElem.getText();
});
return webdriver.promise.all(results);
});
flow.execute(function() {
return attrVals.then(function(res) {
console.log(res[0]);
});
});
return true;
};
driver.findElements(webdriver.By.css('.example_result li')).then(function(arr) {
var result = arr.map(function(webElem) {
var webElemsPromise = webdriver.promise.fulfilled(webElem).then(function(webElem) {
return [webElem];
});
return webdriver.promise.fullyResolved(printTexts(webElemsPromise));
});
return webdriver.promise.all(result);
})
driver.quit(); |
fyi, this is pending SeleniumHQ/selenium#796 |
NOTE - the pending issue is still pending, but with WebDriverJS 2.47 out and other issues beginning to crop up because of the stale version of WebDriverJS (such as install warnings with node.js 4.1 and errors with new browsers when using |
Update selenium-webdriver to 2.47.0 from 2.45.1. This update introduces a convoluted situation where some tests in Proractor's suite would hang - see angular/protractor#2245 This change includes a fix for those issues which removes the explicit `flow.execute` wrapper around `expect` calls. This appears not to introduce any issues to existing tests.
Update: I've release a new version of There is one lingering failure in our test suite, which is that elementExplorer no longer works. The server starts, but is shut down immediately. I've confirmed that this is due to the |
See #2559 |
Done with #2559. |
This will fix several issues, but is currently blocked because
selenium-webdriver
node module @ 2.46.0 is causing issues withElementArrayFinder.each
, probably due to control flow changes.The text was updated successfully, but these errors were encountered: