Railsers: We TDD by using a command, like autotest, which triggers a test run each time we save our documents. This provides perfect test-driven development; we make the smallest testable change possible, predict the results, hit <F5> to save the change, and watch the test transcript. However, test:recent runs our database outside its performance envelop. Our database thinks that setting up a new schema is a rare event. So the db:test:prepare command sometimes takes longer than the actual test run! That, in turn, slows down our TDD cycle, by making us hesitate to hit <F5>. What''s a clean and productized way to knock db:test:prepare, and its ilk, out of test:recent, while keeping it in the raw ''rake test'' command? -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---