# Drake vs the standard Rails Rakefile

**URL:** <https://www.ruby-forum.com/t/drake-vs-the-standard-rails-rakefile/163459>\
**Category:** Rails\
**Created:** [March 20, 2009, 4:33pm UTC](https://www.ruby-forum.com/t/drake-vs-the-standard-rails-rakefile/163459 "2009-03-20T16:33:14Z")\
**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:** [March 20, 2009, 4:33pm UTC](https://www.ruby-forum.com/t/drake-vs-the-standard-rails-rakefile/163459/1 "2009-03-20T16:33:14Z")

</div>

Railsters:

I tried to stop them, but my colleagues have added way too many unit  
tests to  
our projects.

Because we are underusing our multi-core CPUs, I would like to speed the  
test  
run up by soaking the unit tests in one thread and the functional tests  
in another.

drake is a rake clone which offers the seq[:task1, :task2] command, to  
run the  
two tasks in two cores.

Has anyone tried this with the standard Rails Rakefile? and would like  
to share  
some scripts? that maybe show how to keep the database happy?

I will post back here what I discover while trying to do this!

–  
Phlip