EES-4444 Swap pyderman for webdriver-manager #4254
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes the downloading of Chromedriver to use webdriver-manager instead of pyderman. This was motivated by a recent change to how Chromedriver downloads are published, meaning that JSON endpoints should be called for correct versions: https://github.com/GoogleChromeLabs/chrome-for-testing#json-api-endpoints
Currently, webdriver-manager supports this, but pyderman does not. See:
Webdriver download directory
Note that a major difference with pyderman is that Webdrivers are now installed globally to your home directory in the
~/.wdm
directory. The currentwebdriver
directory in the project itself is now redundant and will not actually be used.