August 16. 2009 15:09

Hi Andrew

Ha ha the sign is great!

I'm not sure but the reason why NMock2 gives the observed order of errors might be either of
- the unit test runner you use (R# may act stangely)
- the error is rethrown because VerifyAllExpectations is executed and will rethrow an unexpected invocation exception

But maybe, I'm just used too much to the way it is
I'll have a look at that.

Maybe you can post about your thoughts in which scenarios which framework does the best job. That would be great input to provide better error messages.

Cheers,
Urs

Urs Enzler - NMock2 Dev Team

August 31. 2009 13:17

Hi Urs,

Finally I got to it. So a few observations from me here:

1. Custom messages are faily important. It's a place for Isolator to catch up.

2. Isolator makes a terrific job by telling "Foo was called with unexpected parameters" - all others just say "Foo was not called". A place to catch up for others

3. More detailed error messages just feel better - I prefer "Foo was expected to be called 5 times but was called 6" instead of a less verbose "Foo: actual 5, expected 6". Error messages aren't something we should see often, so brevity probably shouldn't be their strong suit.

That's that - happy mocking!

Andrew