On Mon, Mar 30, 2009 at 2:35 AM, Matt Wynne <m...@mattwynne.net> wrote: > > On 29 Mar 2009, at 20:18, Stephen Eley wrote: > >> # This line ensures that RSpec will run in the 'test' environment >> # regardless of defaults set by other tools. If you have reasons to run >> # specs in other environments, you can allow this value to be overridden >> # by changing the line to: >> # >> # ENV['RAILS_ENV'] ||= 'test' > > > Just to explain: I think it was me who asked for this, though the change > wasn't in generated code, it was in a file in rspec-rails that gets run when > you require 'spec/rails'. We use a 'features' environment for running our > features (so we can run them in parallel with specs) and it was causing some > weird behaviour as the constant was changing under our feet as the features > (which use some rspec-rails matchers) were run.
What was the code doing to make the rspec-rails matchers available? There's no reason you'd need to load 'spec/spec_helper.rb' to do that. > > Matt Wynne > http://beta.songkick.com > http://blog.mattwynne.net > > > > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
