@Pure.Krome: good response but I will add a few details @Kevin: You have to choose a solution depending on the changes that you can bring to the code. If you can change it, some dependency injection make the code more testable. If you can’t, you need a good isolation. With free mocking framework (Moq, RhinoMocks, … 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.
Using Moq: var request = new Mock<HttpRequestBase>(); // Not working – IsAjaxRequest() is static extension method and cannot be mocked // request.Setup(x => x.IsAjaxRequest()).Returns(true /* or false */); // use this request.SetupGet(x => x.Headers).Returns( new System.Net.WebHeaderCollection { {“X-Requested-With”, “XMLHttpRequest”} }); var context = new Mock<HttpContextBase>(); context.SetupGet(x => x.Request).Returns(request.Object); var controller = new YourController(); controller.ControllerContext = … Read more
Moq cannot mock non virtual methods on classes. Either use other mocking frameworks such as Type mock Isolator which actually weaves IL into your assembly or place an interface on EmailService and mock that.
HttpClient’s extensibility lies in the HttpMessageHandler passed to the constructor. Its intent is to allow platform specific implementations, but you can also mock it. There’s no need to create a decorator wrapper for HttpClient. If you’d prefer a DSL to using Moq, I have a library up on GitHub/Nuget that makes things a little easier: … Read more
HttpContext is read-only, but it is actually derived from the ControllerContext, which you can set. controller.ControllerContext = new ControllerContext( context.Object, new RouteData(), controller );
For ‘out’, the following seems to work for me. public interface IService { void DoSomething(out string a); } [TestMethod] public void Test() { var service = new Mock<IService>(); var expectedValue = “value”; service.Setup(s => s.DoSomething(out expectedValue)); string actualValue; service.Object.DoSomething(out actualValue); Assert.AreEqual(expectedValue, actualValue); } I’m guessing that Moq looks at the value of ‘expectedValue’ when you … Read more
Extension methods are just static methods in disguise. Mocking frameworks like Moq or Rhinomocks can only create mock instances of objects, this means mocking static methods is not possible.
I have used a Wrapper to get around this problem. Create a wrapper object and pass your mocked method. See Mocking Static Methods for Unit Testing by Paul Irwin, it has nice examples.