Closed bcharna closed 5 years ago
Looks like you may be missing the chromedriver itself. We use the chromedriver-helper gem in our projects.
@bcharna has this issue been resolved for you?
Yeah, last time I revisited this, I did not encounter the issue. Thank you!
I was noticing some hanging and errors when using the
selenium_chrome_billy
driver in my own app, so I decided to see if the same issue happens in the gem's test suite and it seems it does.First, I simplified the gem's
spec_helper.rb
just to eliminate some completely for this exercise to the following:Note that I kept
Capybara.javascript_driver = :poltergeist_billy
.Then, a spec file is run:
Output
This output is correct and as expected.
However, changing
Capybara.javascript_driver = :poltergeist_billy
toCapybara.javascript_driver = :selenium_chrome_billy
causes the following output when the same command is run:Any insight into why just changing the driver to
selenium_chrome_billy
causes the suite to not pass with the above errors?