Use Chrome for Testing with WebdriverManager for testing web applications#434
Merged
Conversation
ramondevries
approved these changes
Jun 3, 2025
Member
ramondevries
left a comment
ramondevries
left a comment
There was a problem hiding this comment.
Tested during tech meeting. no issues found.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The
--load-extensionflag has been removed in Chrome-branded builds starting from version 137.Reference: Chromium Extensions Google Group Discussion
To address this, we are updating the TESTAR webdriver setup as follows:
--load-extensionflag.ChromeDownloaderclass trying to automate this processIncluded new webdriver classes
WdChromeManagerto use Chrome for Testing + WebDriverManagerWdFirefoxManagerto use Firefox browser + WebDriverManagerWdEdgeManagerto use Edgebrowser + WebDriverManager