-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test fails under Firefox GeckoDriver 0.31.0 #275
Comments
Here's the workaround I used: Since this was fixed with "resolutions": {
"webdriverio": "^7.19.5"
} Ensure with
And then you can use the sl_firefox_latest: {
base: "SauceLabs",
browserName: "firefox",
browserVersion: "latest",
"moz:debuggerAddress": true
}, This way you don't need to set the "sauce:options": {
geckodriverVersion: "0.30.0"
} |
Implement the steps described on the following pages: - karma-runner/karma-sauce-launcher#275 - https://saucelabs.com/resources/blog/update-firefox-tests-before-oct-4-2022
Implement the steps described on the following pages: - karma-runner/karma-sauce-launcher#275 - https://saucelabs.com/resources/blog/update-firefox-tests-before-oct-4-2022
For future reference, it appears that the Thanks to everyone for the super-useful info, this thread has been gold! |
We tried the workaround by using webdriverio different versions(latest to 7.19.5) in resolutions and direct dependency also but still facing the same issue. Can anyone help us by providing any suggestion or workaround. Thanks in advance. |
For future reference, I got around this issue by adding the following to the
|
Since Sauce Labs updated (10/04/22) the Firefox GeckoDriver to version 0.31.0 our tests are failing in CI in several projects that runs some integration tests against Firefox latest.
After some investigation, it turns out that the deprecated capability highlighted in the article,
--remote-debugging-port
, is being sent by thewebdriverio
package as you can see here which prevent the driver of being instantiated and hence the session of being created as the server refuses to initiate the session when receiving an invalid capability.CI logs
SauceLabs test logs
Request playload to the
/session
endpoint:The server returns an HTTP 500 status code with the following cause:
Proposal solution
To fix this issue, we should update the
webdriverio
dependency so that the deprecated capability isn't sent at all.This has been fixed in webdriverio/webdriverio#8211 but I believe this has been shipped only since
webdriverio@^7.19.5
.FYI @christian-bromann
The text was updated successfully, but these errors were encountered: