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
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.
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
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.