From c29cfe13b4a0a7dc9d23bdddee70dda5c6519c28 Mon Sep 17 00:00:00 2001 From: Alex Kotov Date: Sun, 9 Dec 2018 05:38:41 +0500 Subject: [PATCH] Fix code style --- features/support/env.rb | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-) diff --git a/features/support/env.rb b/features/support/env.rb index 0e38d7f..4c46936 100644 --- a/features/support/env.rb +++ b/features/support/env.rb @@ -7,8 +7,8 @@ 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. +# instead of editing this one. Cucumber will automatically load all +# features/**/*.rb files. require 'cucumber/rails' require 'capybara-screenshot/cucumber' @@ -23,13 +23,13 @@ Capybara.javascript_driver = :webkit # 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. +# 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: +# 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 # @@ -39,15 +39,18 @@ Capybara.javascript_driver = :webkit ActionController::Base.allow_rescue = false # Remove/comment out the lines below if your app doesn't have a database. -# For some databases (like MongoDB and CouchDB) you may need to use :truncation instead. +# For some databases (like MongoDB and CouchDB) +# you may need to use :truncation instead. begin DatabaseCleaner.strategy = :transaction rescue NameError - raise 'You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it.' + raise 'You need to add database_cleaner ' \ + 'to your Gemfile (in the :test group) if you wish to use it.' end -# You may also want to configure DatabaseCleaner to use different strategies for certain features and scenarios. -# See the DatabaseCleaner documentation for details. Example: +# You may also want to configure DatabaseCleaner to use different strategies +# for certain features and scenarios. See the DatabaseCleaner documentation +# for details. Example: # # Before('@no-txn,@selenium,@culerity,@celerity,@javascript') do # # { except: [:widgets] } may not do what you expect here @@ -56,12 +59,12 @@ end # DatabaseCleaner.strategy = :truncation # end # -# Before('not @no-txn', 'not @selenium', 'not @culerity', 'not @celerity', 'not @javascript') do +# Before('not @no-txn', 'not @selenium', 'not @culerity', 'not @celerity', +# 'not @javascript') do # DatabaseCleaner.strategy = :transaction # end # # Possible values are :truncation and :transaction # The :transaction strategy is faster, but might give you threading problems. -# See https://github.com/cucumber/cucumber-rails/blob/master/features/choose_javascript_database_strategy.feature Cucumber::Rails::Database.javascript_strategy = :truncation