You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 5, 2022. It is now read-only.
Feature specs don't work with Docker. You should be able to write a test with js: true and run docker-compose run web rspec successfully. What happens instead is that you get this error message:
Selenium::WebDriver::Error::WebDriverError:
Unable to find chromedriver. Please download the server from http://chromedriver.storage.googleapis.com/index.html and place it somewhere on your PATH. More info at https://github.com/SeleniumHQ/selenium/wiki/ChromeDriver.
EEC's Dockerfile has some lines about ChromeDriver which could be useful.
The text was updated successfully, but these errors were encountered:
Do we want the Dockerfile to support running the app in development/test? Personally I've never found that to be a productive environment and I know a decent amount of folks have the same sentiment. That being said, is this closable?
I personally don't find that to be a desirable state (I don't want to, nor do I, run tests inside my docker container), yet I am but one person. I get the generic appeal, but I don't think it actually helps very much.
See this comment.
Feature specs don't work with Docker. You should be able to write a test with
js: true
and rundocker-compose run web rspec
successfully. What happens instead is that you get this error message:EEC's Dockerfile has some lines about ChromeDriver which could be useful.
The text was updated successfully, but these errors were encountered: