> I would just hit the database. That's the conclusion that I reached a while back as well which is why I've been doing it for so long.
The thing that annoys me is I read through a book like Continuous Testing (http://pragprog.com/book/rcctr/continuous-testing) and they say you should be aiming for your tests to run fast enough to have hundreds running per second. That's all well and good for code that isn't hitting external services (database, file system) but within a rails application it just doesn't seem at all feasible and still keep a solid test suite. If anyone has any more tips on when to mock/stub within a rails application or how to speed up a test suite I would love to hear it. Scott -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
