Griffin, NMock takes a different approach to DotNetMock.
Both libraries are pretty much direct ports of existing libraries;
DotNetMock comes from the main Java MockObjects library, whereas NMock
comes from JMock and PythonMock that Nat Pryce wrote (in the nat module).
NMock uses dynamic bytecode generation to create mocks at runtime which are
configured by the unit-tests.
The DotNetMock library is better suited for hand-rolled mocks as it is very
flexible and customizable whereas NMock is for when you need something
quick'n'dirty. I'd imagine the DotNetMock project to also supply a set of
existing mock implementations for common .NET libraries.
I think a lot can be gained from combining our efforts to get the best of
both worlds (the dynamic stuff and predicate library from NMock with the
expectation library from DotNetMock).
Cheers,
-joe
Joe Walnes, ThoughtWorks
At 18:57 06/10/2002 -0500, Griffin Caprio wrote:
>I see that there is a NMock project in the mockobject-java source tree.
>Darren Hobbs and I are already working on a .NET Mock Objects project on
>sourceforge (http://www.sourceforge.net/projects/dotnetmock). We already
>have the core framework implemented. Our first release will be this week,
>once we polish the build and documentation process. After that we are
>hoping for community input as to what to implement next.
>
>Is NMock an exact replication of the java mock objects?
>
>If so, can I suggest that we combine our efforts, so as not to create
>competing .NET Mock Object Implementations?
|
