Running Capybara tests with Chrome, both locally and on Travis

.configure_capybara.rb

require 'selenium-webdriver'
require 'capybara/rspec'
require 'capybara/dsl'
require 'capybara-screenshot/rspec'

Capybara.register_driver :chrome do |app|
  options = Selenium::WebDriver::Chrome::Options.new
  options.add_preference :download, {
      prompt_for_download: false,
      default_directory: 'tmp/downloads'
  }
  Capybara::Selenium::Driver.new(app, browser: :chrome, options: options)
end

Capybara::Screenshot.register_driver(:chrome) do |driver, path|
  driver.browser.save_screenshot(path)
end

Capybara.javascript_driver = :chrome

Capybara.default_max_wait_time = 5
Capybara.default_driver = :chrome
Capybara.save_path = 'tmp/screenshots'

.configure_rspec.rb

RSpec.configure do |config|
  config.expect_with :rspec do |expectations|
    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
  end

  config.mock_with :rspec do |mocks|
    mocks.verify_partial_doubles = true
  end

  config.shared_context_metadata_behavior = :apply_to_host_groups
end

.travis.yml

# We need this because Chrome fails to start in Travis' container infrastructure due to their tight resource
# constraints.
sudo: required

addons:
  chrome: stable

language: ruby

before_script:
  - "export DISPLAY=:99.0"
  - "sh -e /etc/init.d/xvfb start" # We need xvfb - X Virtual FrameBuffer - to support applications requiring
                                   # graphical interfaces, such as Chrome. We do not run Chrome in headless mode, but
                                   # if we were, we would still need xvfb.
  - sleep 10                       # Give xvfb some time to start.

before_install:
  - gem update --system
  - gem --version

script:
  - bundle exec rake test_all