Expect.Call(() => carRepository.FindById(expectedId))
.Return(something)
.Message(“CarRepository.FindById isn't called”);

or with the AAA syntax
CarRepository.AssertWasCalled( x => x.FindById(expectedId));

or with Moq
CarRepositoryMock.Setup(x => x.FindById(expectedId))
.Returns(something);

The reason ppl don't give examples on parameterized repository method test is because it is NOT a part of MVC. You should google for “examples unit testing”. That is just the basics of unit testing.

interface IProduct{

IProduct GetProductId(int id);
}

Every where people use tests on GetAllProducts(). How can one test using Moq or generate implementations to test a method such as in the interface above.

There is something wrong with Moq testing according to my understanding. Why is every body using GetAll() as a representation of the Moq tests in Repository methods, yet methods that take paramters should be tested. Does any one understand MVC out there??? I truly don't see why nobody gives an example of parametized Repository method tests…..

Thansk for comment. Are you from Dubai?. I am also from Dubai, Working in Emirates Airline IT Dept.

Sanjeev

That’s why it’s called ‘unit’ testing right? (-:

Thanks for the links.

I specifically enjoy the 2nd link by Peter Provost. He uses the same technique to implement Model View Presenter / Supervising Controller in the article.

Looking forward to read ur posts on it.

I’m going to write about mocking also, in my Unit Testing series. Unfortunately, to me… to find a perfect time to start writing is rather harder than to sleep : ( at least, for recently.

There are two articles in CodeProject I like the most, talking about Unit Testing. The first one is Advanced Unit Testing series by Marc Clifton: http://www.codeproject.com/KB/cs/autp1.aspx, and the second one is Test-Driven Development in .NET by Peter Provost: http://www.codeproject.com/KB/dotnet/tdd_in_dotnet.aspx.

We can find Peter shows another example how to test a controller in the second link I just gave.

However, unit testing is intended to be well isolated from any external parts of the target object. That’s why mock object come up with such a cool job.