You could probably create a test case or two, time them and then estimate total time based on that. If you are planning on using in-memory sqlite then it might be quicker than what you'd expect. Ever since I moved to doing in-memory testing my tests run in about half the time it used to take. Granted, my biggest project so far has around 20 tables or so, ymmv.
------------------------------------------------------------------ Enrique Ramirez Irizarry Lead Developer, Codabytes Consulting Group http://www.Codabytes.com Personal Page: http://www.indiecodelabs.com On Mon, May 4, 2009 at 3:05 AM, Peter Morris <[email protected]> wrote: > > > Sorry, I don't understand the question... Can you clarify further? > > Here is the context: > http://ayende.com/Blog/archive/2009/04/28/nhibernate-unit-testing.aspx > > Will creating the DB structure for each test take a long time when there > are > 200 tables. > > > Pete > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
