Frederick Cheung wrote: > >> I find the rake db:migrate commands to be less than comprehensive here. >> Sometimes one rake command understands testing, but another one does not.
> If you run > > rake > > to run your unit tests, that should clone the structure from the > development database to the test one. Maybe we do the trick too often where we add a migration, then run the one test waiting for it. That resolves to: ruby test/unit/foo_test.rb -n test_bar ...which utterly bypasses all rake scripts. But our projects are old, so their scripts might not be well tuned. Then I don't know what the OP's real problem is, but 'rake RAILS_ENV=test db:migrate' is well-worth a shot! -- Phlip --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
