44 lines
1.7 KiB
Ruby
44 lines
1.7 KiB
Ruby
# frozen_string_literal: true
|
|
|
|
# This should be on the top of the file.
|
|
$coverage = true
|
|
require 'simplecov'
|
|
|
|
# IMPORTANT: This file is generated by cucumber-rails - edit at your own peril.
|
|
# It is recommended to regenerate this file in the future when you upgrade to a
|
|
# newer version of cucumber-rails. Consider adding your own code to a new file
|
|
# instead of editing this one. Cucumber will automatically load all
|
|
# features/**/*.rb files.
|
|
|
|
require 'cucumber/rails'
|
|
require 'capybara-screenshot/cucumber'
|
|
|
|
Capybara.default_driver = :rack_test
|
|
Capybara.javascript_driver = :selenium_headless
|
|
|
|
Capybara::Screenshot.register_driver :selenium_headless do |driver, path|
|
|
driver.browser.save_screenshot path
|
|
end
|
|
|
|
# Capybara defaults to CSS3 selectors rather than XPath.
|
|
# If you'd prefer to use XPath, just uncomment this line and adjust any
|
|
# selectors in your step definitions to use the XPath syntax.
|
|
# Capybara.default_selector = :xpath
|
|
|
|
# By default, any exception happening in your Rails application will bubble up
|
|
# to Cucumber so that your scenario will fail. This is a different from how
|
|
# your application behaves in the production environment, where an error page
|
|
# will be rendered instead.
|
|
#
|
|
# Sometimes we want to override this default behaviour and allow Rails to rescue
|
|
# exceptions and display an error page (just like when the app is running
|
|
# in production). Typical scenarios where you want to do this is when you test
|
|
# your error pages. There are two ways to allow Rails to rescue exceptions:
|
|
#
|
|
# 1) Tag your scenario (or feature) with @allow-rescue
|
|
#
|
|
# 2) Set the value below to true. Beware that doing this globally is not
|
|
# recommended as it will mask a lot of errors for you!
|
|
#
|
|
ActionController::Base.allow_rescue = false
|