|
From: Steve F. <st...@m3...> - 2003-09-18 07:14:34
|
glad you like it. We haven't found this to be a problem yet. I guess the invitable question is have you profiled your tests and found the proportion of time this takes? I suppose it could be done, but you'd have to be careful about making sure that the mock class is regenerated when the original changes. S. Jeremy wrote: > I just discovered NMock, and am darned glad to see it. I'm in the > process of writing some unit tests for code which runs against a > particularly poorly designed 3rd-party interface, and was painfully > implementing some mocks for it. > > But (you knew that was coming) I am concerned with the test run-time > overhead of dynamically generating a mock over a given type. > > I was wondering how difficult it would be to serialize the generated > type into code? I don't see any obvious way to do it, but I thought > I might be missing something. > > I'd like to be able to dynamically generate a mock, then store the > generated mock as code for later use. > > If I had a clue to go about it, I'd submit the feature code myself. > ;) > > Thanks for the great work! I'm quite excited about it. -Jeremy -- "A LISP programmer knows the value of everything but the cost of nothing. A C programmer knows the cost of everything but the value of nothing." (Todd Proebsting) |