Skip to content
This repository was archived by the owner on May 5, 2022. It is now read-only.

ChromeDriver with Docker #36

Closed
zfletch opened this issue Oct 9, 2017 · 4 comments
Closed

ChromeDriver with Docker #36

zfletch opened this issue Oct 9, 2017 · 4 comments

Comments

@zfletch
Copy link
Contributor

zfletch commented Oct 9, 2017

See this comment.

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.

@BlakeWilliams
Copy link
Contributor

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?

cc @kevin-j-m

@kevin-j-m
Copy link
Contributor

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.

@BlakeWilliams
Copy link
Contributor

Okay, thoughts on closing this until someone shows interest or opens a PR?

@kevin-j-m
Copy link
Contributor

As always, issues and PRs are welcome.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants