Would it be faster to create 200 tables in a real database per test and drop them afterwards?
Perhaps it would be faster to mock repositories to serve only the entities required for testing, but this doesn't allow you to test cascading, uniqueness and other constraints of data access. However, for domain-only test-cases, mocked repositories might be better for testing, especially with a large number of database objects. -Markus 2009/5/3 mhnyborg <[email protected]> > > I love the idea of in memory test. > > But can it be don if the database has 200 tables? I men does it take > to long. > > Hope to here from someone that have tried it. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
