env.rb

# 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 'rubygems'
require 'spork'

Spork.prefork do
  require 'cucumber/rails'
  require "factory_girl/step_definitions"
  require 'cucumber/rspec/doubles'
  require 'yaml'

  # Short circuits omniauth
  # https://github.com/intridea/omniauth/wiki/Integration-Testing
  OmniAuth.config.test_mode = true

  # Capybara defaults to XPath selectors rather than Webrat's default of CSS3. In
  # order to ease the transition to Capybara we set the default here. If you'd
  # prefer to use XPath just remove this line and adjust any selectors in your
  # steps to use the XPath syntax.
  Capybara.default_selector = :css
  Capybara.app_host = 'http://localhost:3000'

  # Functional users
  CONFIG = YAML.load_file '/etc/blog/blog.conf'
  PASS = Encryptor.decrypt("\x8A2\x89\x9A\xB1\xC2\xD12<\xBAj\xC5\x03D\x15R", :key => CONFIG['salt'])
  FUNCTIONAL_USERS = { 'normal user'                => {:name => 'Normal User',  :email => 'blogfunctional1@gmail.com', :pass => PASS, :uid => '1'},
                       'admin'                      => {:name => 'Admin User',   :email => 'blogfunctional2@gmail.com', :pass => PASS, :uid => '2'},
                       'poker player'               => {:name => 'Poker Player', :email => 'blogfunctional3@gmail.com', :pass => PASS, :uid => '3'},
                       'user with an email address' => {:name => 'Gots Email',   :email => 'blogfunctional4@gmail.com', :pass => PASS, :uid => '4'}}
end

Spork.each_run do
  # 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

  # 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.
  #begin
    #require 'database_cleaner'
    #require 'database_cleaner/cucumber'
    #DatabaseCleaner.strategy = :truncation
  #rescue NameError
    #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:
  #
  #   Before('@no-txn,@selenium,@culerity,@celerity,@javascript') do
  #     DatabaseCleaner.strategy = :truncation, {:except => %w[widgets]}
  #   end
  #
  #   Before('~@no-txn', '~@selenium', '~@culerity', '~@celerity', '~@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

end