Skip to content

Update javascript driver to headless chrome #796

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

Merged
merged 3 commits into from
Oct 1, 2017
Merged

Update javascript driver to headless chrome #796

merged 3 commits into from
Oct 1, 2017

Conversation

BookOfGreg
Copy link
Member

@BookOfGreg BookOfGreg commented Sep 30, 2017

Been having trouble installing the correct combinations of yarn, node (7.x), and phantomJS (2.1.1) to make the tests run smoothly on other computers. Even though I have the same versions, Cliver has decided not to load Phantom on certain machines.

Decided it would make developing this gem easier for other new people if everything they needed was in the Gemspec which you can do with headless chrome. Which is also the most up to date option.
Based on: https://robots.thoughtbot.com/headless-feature-specs-with-chrome and https://docs.travis-ci.com/user/gui-and-headless-browsers/

@BookOfGreg
Copy link
Member Author

Wow, this actually doubles the build speed from 1h25 to 45 minutes for travis.

@rmosolgo
Copy link
Member

rmosolgo commented Oct 1, 2017

😍 So nice to get that download out of the CI build and put all the deps in the gemspec!

@BookOfGreg
Copy link
Member Author

The one 'hidden' dep is Chrome/Chromium itself. If we're happy with that (maybe I should document it) then we could merge this.

@rmosolgo
Copy link
Member

rmosolgo commented Oct 1, 2017 via email

@BookOfGreg BookOfGreg merged commit e2b435d into reactjs:master Oct 1, 2017
@BookOfGreg BookOfGreg deleted the update-to-chromedriver-for-js-tests branch October 1, 2017 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants