moq

I have a unit test fixture in which I'm trying to test a ControllerAction on an ASP.NET MVC controller that's used for membership functions on a web app. I'm trying to mock the HttpContext for the tests. The ControllerAction under test actually sets properties on the HttpContext, such as Session values, Response.Cookies values, etc. This isn't all of the code, but here is a rough sample of the test that I'm trying to get to run: [Test] public void ValidRegistrationDataSuccessfullyCreatesAndRegistersUser() { var context = new Mock<HttpContextBase>() {DefaultValue = DefaultValue.Mock}; context

Recently, I've begun to use Moq to unit test. I use Moq to mock out classes that I don't need to test. How do you typically deal with static methods? public void foo(string filePath) { File f = StaticClass.GetFile(filePath); } How could this static method, StaticClass.GetFile() get mocked? P.S. I'd appreciate any reading materials you recommend on Moq and Unit Testing. Pure.Krome Mocking frameworks like Moq or Rhinomocks can only create mock instances of objects, this means mocking static methods is not possible. You can also search Google for more info. Also, there's a few questions

I've got an interface which declares Task DoSomethingAsync(); I'm using MoqFramework for my tests: [TestMethod()] public async Task MyAsyncTest() { Mock<ISomeInterface> mock = new Mock<ISomeInterface>(); mock.Setup(arg => arg.DoSomethingAsync()).Callback(() => { <my code here> }); ... } Then in my test I execute the code which invokes await DoSomethingAsync() . And the test just fails on that line. What am I doing wrong? Panagiotis Kanavos Your method doesn't have any callbacks so there is no reason to use .CallBack() . You can simply return a Task with the desired values using .Returns() and

or can the class be implementing an abstract class also? To mock a type, it must either be an interface (this is also called being pure virtual ) or have virtual members (abstract members are also virtual). By this definition, you can mock everything which is virtual . Essentially, dynamic mocks don't do anything you couldn't do by hand . Let's say you are programming against an interface such as this one: public interface IMyInterface { string Foo(string s); } You could manually create a test-specific implementation of IMyInterface that ignores the input parameter and always returns the same

I have some issues trying to wrap my code to be used in unit tests. The issues is this. I Have the interface IHttpHandler: public interface IHttpHandler { HttpClient client { get; } } And the class using it, HttpHandler: public class HttpHandler : IHttpHandler { public HttpClient client { get { return new HttpClient(); } } } And then the Connection class, which uses simpleIOC to inject the client implementation: public class Connection { private IHttpHandler _httpClient; public Connection(IHttpHandler httpClient) { _httpClient = httpClient; } } And then I have a unit test project which has