I am certain that running: rake test RAILS_ENV=<some_other_env_than_test>
should work, assuming that I have a correct DB setup in config/database.yml. But this is not happening. It looks like rake test always is using the "test" DB no matter what. If I type rake test RAILS_ENV=crap or RAILS_ENV=crap; rake test my tests will happily run and ignore the value of RAILS_ENV that I'm trying to provide. What gives? Did something change about running tests? Perhaps it's always been this way and I never realized it. Thanks, Wes -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
