-
Notifications
You must be signed in to change notification settings - Fork 113
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
Can we have a WD_CHROME_PATH ENV variable that sets chrome binary path? #137
Comments
Yeah, I was planning to do that. Will work on it this weekend. |
@tchia04 Can you please load this gem from the
|
Hi @kapoorlakshya My test setup However when I ran it without the special handling from below, I got ======== An error occurred in an after hook ▽ Once I force WD_CHROME_PATH env to Selenium::WebDriver::Chrome.path then the webdriver sesssion got created successfully because the chrome and chromedriver version matches.
I am testing with
|
I think the problem is that You'll need Edit: |
Ok. I though the webdriver is a layer on top of Selenium so I don't have do deal with the Selenium configurations. Actually I found that Mac is not working when I tries to use chrome 76 so both Mac and Linux needs
|
WebDrivers was originally designed to manage getting the correct version of the driver to match the browser you're using. It wasn't designed to manage configuring the browser. |
And since |
Ok. Thanks for the explantion @twalpole @kapoorlakshya |
@tchia04 Just released v4.1.0. |
Summary
Set Selenium::WebDriver::Chrome.path to ENV['WD_CHROME_PATH'] if it's defined.
This is similar to the WD_INSTALL_DIR env var for Webdrivers.install_dir
Debug Info
Please provide the following information for bug reports:
Expected Behavior
If WD_CHROME_PATH is defined, then use that for Selenium::WebDriver::Chrome.path
Otherwise, use the default location.
Actual Behavior
Currently I have to muck around my spec_helper.rb but it would be nice to have this as part of webdriver itself to be consistent with WD_INSTALL_DIR
The text was updated successfully, but these errors were encountered: