-
Notifications
You must be signed in to change notification settings - Fork 174
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
Force resolution of selenium-webdriver to 4.10.0 #1541
Conversation
Signed-off-by: Craig Perkins <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #1541 +/- ##
=======================================
Coverage 66.06% 66.06%
=======================================
Files 93 93
Lines 2328 2328
Branches 310 310
=======================================
Hits 1538 1538
Misses 722 722
Partials 68 68 |
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.
Thanks for the fix @cwperks ! I just have a quick question.
"selfsigned": "^2.0.1", | ||
"typescript": "4.0.2" | ||
}, | ||
"dependencies": { | ||
"@hapi/cryptiles": "5.0.0", | ||
"@hapi/wreck": "^17.1.0", | ||
"html-entities": "1.3.1" | ||
}, | ||
"resolutions": { | ||
"selenium-webdriver": "4.10.0" |
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.
Nit: Was there any pkgs dpending on the selenium-webdriver with different versions? Just trying to figure out why we are using the selective dependencies resolution here.
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 is forcing to 4.10.0 due to a suspected bug in selenium. See the versions here: https://www.npmjs.com/package/selenium-webdriver?activeTab=versions
4.11.0 was published 3 days ago and 4.11.1 2 days ago. We can try removing this forced resolution on future versions of selenium. I'm going to look through the selenium issue list to look for any known issues: https://github.com/SeleniumHQ/selenium/issues
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.
I suspect that the error comes from this PR in Selenium, but I don't know enough about selenium to be able to determine why it produces the error we are seeing.
Signed-off-by: Craig Perkins <[email protected]> (cherry picked from commit 95f316a)
Signed-off-by: Craig Perkins <[email protected]> (cherry picked from commit 95f316a) Co-authored-by: Craig Perkins <[email protected]>
…1541) Signed-off-by: Craig Perkins <[email protected]> Signed-off-by: Sam <[email protected]>
Description
Fixes an issue with the Integration Tests that were failing with selenium-webdriver 4.11.1. The tests had a bug on determining browser path that would result in it eventually failing with a message
InvalidArgumentError: binary is not a Firefox executable
. See details on linked issue.Category
[Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation]
Test fix
Issues Resolved
#1540
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.