In Verify Moq by default checks reference equality for arguments so it only passes when you provide the same instances (except if you’ve overriden Equals) in your tests and in your implementation. In you case the expectedA.Value just returns the new A { P1 = 1 } created in the test which, of course, isn’t … Read more
You need to pass through the object instance of the mock var mock = new Mock<IBar>(); var foo = new Foo(mock.Object); You can also use the the mock object to access the methods of the instance. mock.Object.GetFoo(); moq docs
Moq’s latest documentation is now available at github wiki page: https://github.com/Moq/moq4/wiki/Quickstart Previously they were on Google Code. As well as the wiki and other online resources, there’s full documentation in Windows .CHM help-file format included in the Moq binary download linked from the Moq homepage.
It is probably correct that only an Expression with the exactly same structure (and literal values) will match. I suggest that you use the overload of Returns() that lets you use the parameters the mock is called with: repoMock.Setup(moq => moq.FindBy(It.IsAny<Expression<Func<Company, bool>>>()) .Returns((Expression<Func<Company, bool>> predicate) => …); In …, you can use predicate to return … Read more
I am using Moq version 3.0.204.1 and SetupSet does is not marked as obsolete for me. However, there are a couple of SetupSet overloads located in MockLegacyExtensions. You can avoid using those and use SetupSet that is defined on the Mock class. The difference is subtle and you need to use Action<T> as SetupSet parameter, … Read more
Using MoQ it looks something like this: var request = new Mock<HttpRequestBase>(); request.Expect(r => r.HttpMethod).Returns(“GET”); var mockHttpContext = new Mock<HttpContextBase>(); mockHttpContext.Expect(c => c.Request).Returns(request.Object); var controllerContext = new ControllerContext(mockHttpContext.Object , new RouteData(), new Mock<ControllerBase>().Object); I think the Rhino Mocks syntax is similar.
VerifyAll() is for verifying that all the expectations have been met. Suppose you have: myMock.Setup(m => m.DoSomething()).Returns(1); mySut.Do(); myMock.VerifyAll(); // Fail if DoSomething was not called
You may wish to change your consuming code to take in an interface for a factory that creates requests and responses that can be mocked which wrap the actual implementation. Update: Revisiting I’ve been getting downvotes long after my answer was accepted, and I admit my original answer was poor quality and made a big … Read more
Using It.IsAny<>, It.Is<>, or a variable all serve different purposes. They provide increasingly specific ways to match a parameter when setting up or verifying a method. It.IsAny The method set up with It.IsAny<> will match any parameter you give to the method. So, in your example, the following invocations would all return the same thing … Read more
The way you prepare the mocked user is the problem. moqUser.Object.Name = username; will not set the name, unless you have setup the mock properly. Try this before assigning values to properties: moqUser.SetupAllProperties(); This method will prepare all properties on the mock to be able to record the assigned value, and replay it later (i.e. … Read more