On 10/18/07, Steve <[EMAIL PROTECTED]> wrote: > On Thu, 18 Oct 2007 15:51:37 +0100, Keith McDonnell wrote: > > > For those interested .... > > > > rake spec:models seems to clone the test database from development. If > > your dev db is empty, the models task fails mysteriously. > > > > Anyway, to make sure your dev db is at the current migration version, I > > added this dependency in lib/tasks > > > > task 'spec:models' => 'db:migrate' > > > > Now the dev db is migrated up with each test pass. > > > > Keith > > Yeah, I was just about to post about this. This seems like incorrect > behavior. Especially if you're really doing behavior driven design. You're > going to be writing your tests and using the test environment first before > you actually go through and use the dev env. When specs are run it should > run all migrations for the test db, not just as far as dev has gone.
Please submit a feature request: http://rubyforge.org/tracker/?group_id=797 _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
