In case it's of interest to anyone I *finally* managed to isolate what was causing this problem.
By uninstalling and reinstalling all of my gems I narrowed the issue down to a conflict between rspec-rails and the "default_value_for" gem. The addition of the default_value_for gem means that "cucumber features" fails with the errors above. It does not affect running "rspec spec" which works fine. I'm not sure which gem is triggering the problem or whether it's the cucumber gem but I've also flagged this to the authors of default_value_for. For a clean installation of Rails, the following gemfile thows errors: ---------------- source :rubygems gem "rake" gem "rails", ">=3.0.7" group :development, :test do # up to date gem "faker" gem "factory_girl_rails" gem "ruby-debug19" gem "capybara", ">= 0.4.1.2" gem 'cucumber-rails' gem 'database_cleaner' gem "rspec-rails" gem "default_value_for" end ---------------- (Apologies if this is the wrong place to post this but I wanted to follow up on my earlier email) -- Posted via http://www.ruby-forum.com/. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
