# Rake test:recent without db:test:prepare

**URL:** <https://www.ruby-forum.com/t/rake-test-recent-without-dbprepare/127975>\
**Category:** Rails\
**Created:** [February 3, 2008, 4:32pm UTC](https://www.ruby-forum.com/t/rake-test-recent-without-dbprepare/127975 "2008-02-03T16:32:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Phlip](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/ed8c4c/32.png) [@Phlip](https://www.ruby-forum.com/u/Phlip)\
**Post date:** [February 3, 2008, 4:32pm UTC](https://www.ruby-forum.com/t/rake-test-recent-without-dbprepare/127975/1 "2008-02-03T16:32:36Z")

</div>

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 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 .

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