Some test tools such as Cucumber (and I'm sure I've seen it in RSpec but I cannot reproduce it right now) do not run the migrations before they run the tests. I think Rails should automatically do it so that when you run the tests the database is already setup. Why run it every time when you should only run it once? This would speed up the execution of the tests.
On 21 September 2010 12:04, Xavier Noria <[email protected]> wrote: > Not sure I follow. > > You do not need an extra task to run migrations in dev and test. > Because the test database is loaded straight from db/schema.rb. > > The flow is: you run db:migrate in the environment you want, say > "development". That dumps db/schema.rb as a side-effect, and the test > tasks load that file. They do not use migrations. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-core%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
