Closed bek-mednax closed 2 years ago
@bek-mednax The workaround is to set only chrome or firefox drivers in the selenium-standalone service options, if you don't need to use edge at all.
config.services = (config.services ? config.services : []).concat([
[
'selenium-standalone',
{
args: {
seleniumArgs: ['--port', '4444']
},
drivers: {
chrome: true // set `true` to use the version provided by `selenium-standalone`, 'latest' by default
}
},
],
]);
@pgagnidze The workaround works perfectly, thank you!
+1 same issue
@helloromero et. al. any contributions to resolve the issue are appreciated. Please get involved, thanks!
Have you read the Contributing Guidelines on issues?
WebdriverIO Version
latest
Node.js Version
7.21.1
Mode
Standalone Mode
Which capabilities are you using?
No response
What happened?
Error in "getDownloadStream". Could not download https://msedgedriver.azureedge.net/96.0.1054.29/edgedriver_mac64.zip See more details below: 404 https://msedgedriver.azureedge.net/96.0.1054.29/edgedriver_mac64.zip Response code 404 (Not Found)
Ended WebDriver sessions gracefully after a SIGINT signal was received!
What is your expected behavior?
I think the broken link from https://msedgedriver.azureedge.net breaking whole framework to execute. Expected behavior is to ignore this broken link because I'm not using even using edgedriver.
How to reproduce the bug.
To reproduce this bug:
Relevant log output
Code of Conduct
Is there an existing issue for this?