env.rb revision d327eb79653cf7820fe583473ab35816d44cd757
52N/A# IMPORTANT: This file is generated by cucumber-rails - edit at your own peril. 52N/A# It is recommended to regenerate this file in the future when you upgrade to a 292N/A# newer version of cucumber-rails. Consider adding your own code to a new file 52N/A# instead of editing this one. Cucumber will automatically load all features/**/*.rb 292N/A # Capybara is smart enough to wait for ajax when not finding elements. 292N/A # In some situations the element is already existent, but has not been updated 292N/A # yet. This is where you need to manually use wait_for_ajax. 52N/A raise "AJAX request took longer than 5 seconds." 52N/A# Capybara defaults to CSS3 selectors rather than XPath. 52N/A# If you'd prefer to use XPath, just uncomment this line and adjust any 292N/A# selectors in your step definitions to use the XPath syntax. 6N/A# By default, any exception happening in your Rails application will bubble up 6N/A# to Cucumber so that your scenario will fail. This is a different from how 6N/A# your application behaves in the production environment, where an error page will 6N/A# be rendered instead. 377N/A# Sometimes we want to override this default behaviour and allow Rails to rescue 377N/A# exceptions and display an error page (just like when the app is running in production). 377N/A# Typical scenarios where you want to do this is when you test your error pages. 377N/A# There are two ways to allow Rails to rescue exceptions: 15N/A# 1) Tag your scenario (or feature) with @allow-rescue 6N/A# 2) Set the value below to true. Beware that doing this globally is not 558N/A# recommended as it will mask a lot of errors for you! 377N/A# For some databases (like MongoDB and CouchDB) you may need to use :truncation instead. 377N/A raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it." 377N/A# You may also want to configure DatabaseCleaner to use different strategies for certain features and scenarios. 377N/A# See the DatabaseCleaner documentation for details. Example: 377N/A# Before('@no-txn,@selenium,@culerity,@celerity,@javascript') do 6N/A# # { :except => [:widgets] } may not do what you expect here 6N/A# Before('~@no-txn', '~@selenium', '~@culerity', '~@celerity', '~@javascript') do 302N/A# Possible values are :truncation and :transaction 6N/A# The :transaction strategy is faster, but might give you threading problems. 121N/A# We need to establish the basic entries in the database