Skip to content
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

System Specs config improvement #53

Merged
merged 4 commits into from
Jun 4, 2018

Conversation

olivierobert
Copy link
Contributor

@olivierobert olivierobert commented May 7, 2018

What happened

The work started due to Chrome driver stability issues (in #51). Upon research and fixing the issues, I found a more complete and also more transparent way to configure Capybara for our projects.

This solution uses the new flag disable-dev-shm-usage available since Chrome 65 (see info). Contrary to #51, it does not require to upgrade to Docker Compose 3.5 ot latest which helps in supporting more CI/CD providers.

Insight

require 'capybara/rspec'

# Give CI some extra time
CAPYBARA_TIMEOUT = ENV['TEST_CI_SERVER'] ? 60 : 30
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While checking the CI services, I notice that most of it have CI=true variable set. Not sure, should we use that variable for checking or not?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great idea. Will change to this variable 👍

…er to conform to the one existing on most CI providers
@olivierobert
Copy link
Contributor Author

@rosle changed in 152a7a9

@olivierobert olivierobert merged commit 0c2ca9b into develop Jun 4, 2018
@olivierobert olivierobert deleted the feature/overhaul-capybara-config branch June 4, 2018 01:31
@rosle rosle mentioned this pull request Jun 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants