|
|
|
@ -1,11 +1,14 @@ |
|
|
|
|
# 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 |
|
|
|
|
# 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 'coveralls' |
|
|
|
|
Coveralls.wear_merged!('rails') |
|
|
|
|
|
|
|
|
|
# Load paths to ensure they are loaded before the plugin's paths.rbs. |
|
|
|
|
# Plugin's path_to functions rely on being loaded after the core's path_to |
|
|
|
|
# function, since they call super if they don't match and the core doesn't. |
|
|
|
@ -27,8 +30,8 @@ Capybara.configure do |config| |
|
|
|
|
end |
|
|
|
|
|
|
|
|
|
# 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 |
|
|
|
|
# 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 |
|
|
|
|