Client code can eat an exception generated by NMock and pass a test that it probably shouldn't. The example code exists in a unit test, but it could just as easily be buried in client code that either was passed the Mock or obtained it through a factory.
example...
//...
Expect.Once.On(aSession).GetProperty("Servers").Will(Return.Value(servers));
DtServerCollection retServers = aSession.Servers; // first call... ok
try
{
retServers = aSession.Servers; // second call... should throw
}
catch
{
//eat the exception...
}
//...
mocks.VerifyAllExpectationsHaveBeenMet(); //this doesn't throw, but probably should; nunit test appears to pass
Logged In: YES
user_id=591527
Originator: NO
Fixed in CVS, a new build should be coming soon.