Hello Salvatore, I think using things like spork or the like is just a band-aid and they are not a solution to the real problem which is the design and mixing things all together in rails provided and known things, specially controllers and models. If we have good design with Single Responsibility Principle and Separation of Concerns we can have incredibly fast tests with focused pieces in our design. And we only need rake or those stuff for running our rails-specific tests (like controller tests, model tests, etc.) and those tests wont need to be run as frequently as domain-logic tests. domain-logic tests should be run so frequently during the red-green-refactor cycle all the time and we should benefit from the quick feedback and other things which are provided by having fast tests.
I recommend you to watch this interesting talk by Corey Haines -> http://arrrrcamp.be/videos/2011/corey-haines---fast-rails-tests/ it'll be great explanation of the things I've just mentioned with perfect details and examples. Hope that helps. Best Regards -- Sam Serpoosh Software Developer: http://masihjesus.wordpress.com Twitter @masihjesus -- 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@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.