From b3dfc73987479e6704e65a122e9044edc65e3f2d Mon Sep 17 00:00:00 2001
From: Stephan Eckardt <s.eckardt@finn.de>
Date: Tue, 15 Mar 2011 11:52:22 +0100
Subject: [PATCH] environment setup is already done in redmine_cucumber

---
 features/support/env.rb | 68 -----------------------------------------
 1 file changed, 68 deletions(-)
 delete mode 100644 features/support/env.rb

diff --git a/features/support/env.rb b/features/support/env.rb
deleted file mode 100644
index ea7d764ee0..0000000000
--- a/features/support/env.rb
+++ /dev/null
@@ -1,68 +0,0 @@
-# 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'
-require 'spec/expectations'
-require 'spec/matchers'
-
-Spork.prefork do
-  ENV["RAILS_ENV"] ||= "cucumber"
-  require File.expand_path(File.dirname(__FILE__) + '/../../config/environment')
-  
-  require 'cucumber/formatter/unicode' # Remove this line if you don't want Cucumber Unicode support
-  require 'cucumber/rails/world'
-  require 'cucumber/rails/active_record'
-  require 'cucumber/web/tableish'
-
-
-  require 'capybara/rails'
-  require 'capybara/cucumber'
-  require 'capybara/session'
-  require 'cucumber/rails/capybara_javascript_emulation' # Lets you click links with onclick javascript handlers without using @culerity or @javascript
-  # 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
-
-end
- 
-Spork.each_run do
-  # If you set this to false, any error raised from within your app will bubble 
-  # up to your step definition and out to cucumber unless you catch it somewhere
-  # on the way. You can make Rails rescue errors and render error pages on a
-  # per-scenario basis by tagging a scenario or feature with the @allow-rescue tag.
-  #
-  # If you set this to true, Rails will rescue all errors and render error
-  # pages, more or less in the same way your application would behave in the
-  # default production environment. It's not recommended to do this for all
-  # of your scenarios, as this makes it hard to discover errors in your application.
-  ActionController::Base.allow_rescue = false
-  
-  # If you set this to true, each scenario will run in a database transaction.
-  # You can still turn off transactions on a per-scenario basis, simply tagging 
-  # a feature or scenario with the @no-txn tag. If you are using Capybara,
-  # tagging with @culerity or @javascript will also turn transactions off.
-  #
-  # If you set this to false, transactions will be off for all scenarios,
-  # regardless of whether you use @no-txn or not.
-  #
-  # Beware that turning transactions off will leave data in your database 
-  # after each scenario, which can lead to hard-to-debug failures in 
-  # subsequent scenarios. If you do this, we recommend you create a Before
-  # block that will explicitly put your database in a known state.
-  Cucumber::Rails::World.use_transactional_fixtures = true
-  # How to clean your database when transactions are turned off. See
-  # http://github.com/bmabey/database_cleaner for more info.
-  if defined?(ActiveRecord::Base)
-    begin
-      require 'database_cleaner'
-      DatabaseCleaner.strategy = :truncation
-    rescue LoadError => ignore_if_database_cleaner_not_present
-    end
-  end
-end