On Mon, Nov 26, 2012 at 12:18 PM, Adam Boas <[email protected]> wrote: > Lots of Factory based (database dependent) unit-level specs
Most rails apps exists solely to shuttle data between the database and the browser. If you are mocking out these interactions you are not really testing the most important part of your application. This is especially true if you have split up your app into multiple classes all of which are interacting with each other and the database. It's expensive sure but it has to be done. BTW once I tried putting the database in a RAM disk for testing purposes, it didn't really help that much so the problem seems to be AR rather than the database itself. -- 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.
