-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fix WebDrivers For Chrome v116+ #427
Conversation
This reverts commit e9dac51.
"If you cannot upgrade to Selenium 4.11, Webdrivers 5.3.0 will continue to support Ruby 2.6+ and Selenium 4.0 - 4.10" - https://github.com/titusfortner/webdrivers
-Needed for webdrivers to work with Chrome v116+
WebMock.disable_net_connect!( | ||
allow_localhost: true, | ||
allow: %w[chromedriver.storage.googleapis.com] | ||
allow: %w[chromedriver.storage.googleapis.com googlechromelabs.github.io edgedl.me.gvt1.com] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will we need to revert this change once we upgrade to ruby 3?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we upgrade to Ruby 3, I'm thinking we should upgrade to Selenium 4.11+.
According to https://github.com/titusfortner/webdrivers:
"If you can update to the latest version of Selenium (4.11+), please do so and stop requiring this gem."
I'm not sure if Selenium will need googlechromelabs.github.io
and edgedl.me.gvt1.com
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds great!
@aaronskiba please add a ticket so we don't forget to follow the suggestions after the upgrade to ruby 3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR addresses the rspec test failures due to the incompatibility between Webdrivers 5.2 and Chrome 116+.