That's an unusual question. The reason you have tests is to verify your code actually does what you think it's doing. If you migrate down, you add and/or remove model attributes, which (hopefully) your code depends on. And your tests should fail if you change that. That is, if your code doesn't break just trying to run the tests.
Are your trying to run a prior version of your app? If so, you should use your revision control system to pull down an older copy of the code and db:reset. HTH On 12/3/08, Shantanu Pavgi <[EMAIL PROTECTED]> wrote: > > After running 'down' some migrations using 'rake db:migrate:down', I am > unable to performs any tests. The message received is: > > You have 3 pending migrations: > 1. blah > 2. blahblah > 3. blahblahblah > Run "rake db:migrate" to update your database then try again. > > > How can I remove (undo) migrations and run tests? > Interestingly, 'similar actions' are working on a different machine. I > remember having the same problem and it disappeared after I experimented > few things with rake:db:migrate. Is there any procedure for removing > migrations? > > Thanks, > Shantanu. > -- > Posted via http://www.ruby-forum.com/. > > > > -- -- James Mitchell --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
