On 26 Feb 2009, at 18:27, Scott T. wrote:
Why not create a new environment, and set RAILS_ENV=“test_cucumber” ?
We do this, and it’s entirely possible, in fact I highly recommend it.
We call our environment ‘features’
One gotcha is that rspec-rails and a certain file in rails (which
cucumber requires into Cucumber::Rails::World) will stomp all over
your RAILS_ENV and set it back to ‘test’, which means that if you do
(and you really shouldn’t) have any code that depends on this being
set correctly, it will break.
I think rspec-rails is now fixed, though you might need to use David’s
latest version from github.
Please let me know how you get on running them in parallel for CI, as
I’d also like to do this. At the moment we just use the two
environments for faster feedback when we’re regressions testing
locally. How are you thinking about collecting the results, for
example? Piping them to separate files?