-1 on changing the tests to be integration tests - I would only do that if
we didn't have confidence in the unit tests.
As for the mocking tool, I've never found a perfect fit (I don't like having
to use .BackToRecord() in Rhino, I don't like having to use .Object in Moq,
etc. etc. etc.) ... which is probably more to do with me being a serial
complainer, than anything to do with the individual frameworks.
So I'm happy to go with any of them (at least, any of the modern ones that
use lambda syntax which Moq does) ... I wouldn't spend time changing the
mocking tool unless there was a distinct advantage (and I haven't seen a
'killer' feature that one has over the other).
P.S., I don't see any (technical) reason that multiple mocking frameworks
can't be used. (Obviously it's not as nice to maintain multiple styles in
future.)
-----Original Message-----
From: Steve Wagner
Sent: Wednesday, April 06, 2011 5:09 AM
To: [email protected]
Subject: Re: [nhibernate-development] Testing with mocks
I can recommend NSubstitute since its syntax, specially the return
syntax is less verbose then the one of Moq. This was a reason for me to
switch.
-Steve
On 06.04.2011 00:33, Fabio Maulo wrote:
Hi.
To test some dozens of classes, in ConfORM, I have used Moq (
http://code.google.com/p/moq/ )
So far I have delayed the choice for one mock framework but perhaps it's
time to choose.
Preferences ?
