Update dependency on selenium-webdriver to 3.7.0 or newer

I have been seeing a lot of random errors like

- Error: ECONNREFUSED connect ECONNREFUSED 127.0.0.1:62416
at ClientRequest.<anonymous> (C:\AzureAgentUI14\_work\4\s\src\Gandalf.Web\node_modules\selenium-webdriver\http\index.js:238:15)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at Socket.socketErrorListener (_http_client.js:387:9)
at emitOne (events.js:116:13)

While exploring this error I found that it is selenium-webdriver that throws the error (as also noted in the error dump above). Protractor relies on selenium-webdriver@3.6.0.

However, in selenium-webdriver@3.7.0 they fixed this issue and implemented a more generic retry feature in case of any network issues with the webdriver socket.

Is there a possibility to update the dependencies on selenium-webdriver? As this would fix some of our problems with unstable tests.

[tbowmo]

@simonua I ended up using https://github.com/ds300/patch-package to patch the http client in selenium-webdriver. Basically just copying over this file to node_modules/selenium-webdriver/http, and create a patch using the patch-package module

You have to edit the index.js after you copied it over, as it doesn’t do retries on ECONNREFUSED out of the box

[tbowmo]

@rene-leanix In our case we needed to add ECONNREFUSED to the retry list as well, as we got frequent issues with that on our azure CI agents.