On Tue, Sep 21, 2010 at 7:27 PM, Jeremy Kemper <[email protected]> wrote: > On Tue, Sep 21, 2010 at 3:08 PM, Ryan Bigg <[email protected]> wrote: > > The test database is ephemeral. Imagine it is created just before the > test run and destroyed just afterward. It is never migrated; it's > cloned on the fly *just for that test run.* > > Anything that expects greater responsibility or longevity from the > test db raises red flags and design smells.
This is a nice ideal. However I agree with others who say that when the schema gets large, recreating it can be slow. And slow tests are a nightmare. What if we could skip db:test:prepare if a NOPREP environment variable is given? Or had an extra set of tasks, say test:quick:unit etc, which skipped it? I've personally taken to doing the former in a large project. George -- 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.
