Difference between MockRepository.GenerateMock<T> and MockRepository.GenerateStub<T>

[changhong]

I use AAA syntax, and I couldn't find any difference between objects
created by MockRepository.GenerateMock<T> or
MockRepository.GenerateStub<T>.

I noticed with both objects, you can setup stubs or expectations using
obj.Stub(..) or obj.Expect(...), for both objects, test won't fail if
an expectation does not happen. Also with both objects, you can verify
an expectation using obj.AssertWasCalled(...), and they behave the
same.

Can anyone tell me what the difference between those two? And how
should I choose one over another?

Manny Thanks.

[Tim Barcz]

There are subtle differences (most of which escape me at the moment).  However you are correct that the notion of a stub and mock as they relate to RhinoMocks has converged over the years.  In the next version of RhinoMocks we're planning to explore the notion of making the two concepts one or at the very least making the distinctions more clear.

Tim

--

You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group.
To post to this group, send email to rhino...@googlegroups.com.
To unsubscribe from this group, send email to rhinomocks+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rhinomocks?hl=en.

--
Tim Barcz
Microsoft C# MVP
Microsoft ASPInsider
http://timbarcz.devlicio.us
http://www.twitter.com/timbarcz

[David Tchepak]

From memory I think the main difference is that GenerateStub<T>
returns an object with normal property behaviour.

For example (psuedo-code only, haven't tested):

var stub = MockRepository.GenerateStub<ISomething>();
stub.MyProperty = 2;
Assert.AreEqual(stub.MyProperty, 2);

If you try the same with a mock then MyProperty would return 0 (or
null for reference type). If you want the property of a mock to return
a specific value you have to stub it (confusing, right? :-)).

var mock = MockRepository.GenerateMock<ISomething>();
mock.MyProperty = 2;
Assert.AreEqual(mock.MyProperty, 0);
mock.Stub(x => x.MyProperty).Return(2);
Assert.AreEqual(mock.MyProperty, 2);

I think that's right, but you should probably run it and make sure I
have a vague idea of what I'm talking about. ;)

My approach is to use GenerateStub<T> everywhere. I don't remember the
last time I needed/wanted the GenerateMock<T> behaviour (at least not
when using AAA style testing).

Hope this helps.
Regards,
David

[changhong]

Thank you very much for your answer.
I have made some tests and they showed exactly the behavior as what
your said.