Issues arise when attempting to run multiple browser windows in Protractor. The code snippet being tested is as follows: I create a new browser instance to perform certain tests. When input is entered into the original browser, it should not affect the newly created one. While everything seems to function properly, the additional browser instance never shuts down after testing and an error message appears in the output.
The test suite:
'use strict';
describe('testing', function () {
it('should work', function () {
browser.get('http://angularjs.org');
var browser2 = browser.forkNewDriverInstance(true);
element(by.name('as_q')).sendKeys('search');
expect(browser2.element(by.name('as_q')).getText()).toBe('');
});
});
Configuration settings:
exports.config = {
framework: 'jasmine2',
capabilities: {
'browserName': 'chrome'
},
baseUrl: 'http://localhost:4000',
specs: 'test.spec.js',
jasmineNodeOpts: {
showColors: true,
defaultTimeoutInterval: 30000
}
};
Output displayed while running Protractor in the terminal:
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://<my-ip-adress>:54721/wd/hub
Started
.
1 spec, 0 failures
Finished in 8.755 seconds
Shutting down selenium standalone server.
/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:145
callback(new Error(message));
^
Error: ECONNREFUSED connect ECONNREFUSED
at ClientRequest.<anonymous> (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:145:16)
at ClientRequest.emit (events.js:95:17)
at Socket.socketErrorListener (http.js:1552:9)
at Socket.emit (events.js:95:17)
at net.js:441:14
at process._tickCallback (node.js:442:13)
From: Task: WebDriver.quit()
at [object Object].webdriver.WebDriver.schedule (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:360:15)
at [object Object].webdriver.WebDriver.quit (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:443:21)
at /usr/local/lib/node_modules/protractor/lib/driverProviders/driverProvider.js:59:14
at [object Object].promise.ControlFlow.runInFrame_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1877:20)
at [object Object].promise.Callback_.goog.defineClass.notify (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:2464:25)
at [object Object].promise.Promise.notify_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:563:12)
at Array.forEach (native)
at Object.goog.array.forEach (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/array/array.js:203:43)
at [object Object].promise.Promise.notifyAll_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:552:16)
at [object Object].goog.async.run.processWorkQueue [as _onTimeout] (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/async/run.js:125:21)
[launcher] Process exited with error code 1
Using Protractor version 2.0.0.
Why does the forked driver instance not close automatically like the main browser does? Is manual closure required before terminating the Selenium server?