-
Notifications
You must be signed in to change notification settings - Fork 25
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
Conversation
…latest flags `disable-dev-shm-usage` for Docker (as of Chrome 65)
shared/rspec/support/capybara.rb
Outdated
require 'capybara/rspec' | ||
|
||
# Give CI some extra time | ||
CAPYBARA_TIMEOUT = ENV['TEST_CI_SERVER'] ? 60 : 30 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
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
export CHROME_HEADLESS=false
. Then reset it:unset CHROME_HEADLESS
.