Mock HttpContext Current in Test Init Method

Question

I m trying to add unit testing to an ASP NET MVC application I have built   In my unit tests I use the following code    TestMethod  public void IndexAction Should Return View         var controller   new MembershipController        controller SetFakeControllerContext  TestUser                 With the following helpers to mock the controller context   public static class FakeControllerContext       public static HttpContextBase FakeHttpContext string username            var context   new Mock lt HttpContextBase gt              context SetupGet ctx   gt  ctx Request IsAuthenticated  Returns  string IsNullOrEmpty username             if   string IsNullOrEmpty username               context SetupGet ctx   gt  ctx User Identity  Returns FakeIdentity CreateIdentity username             return context Object             public static void SetFakeControllerContext this Controller controller  string username   null            var httpContext   FakeHttpContext username           var context   new ControllerContext new RequestContext httpContext  new RouteData     controller           controller ControllerContext   context            This test class inherits from a base class which has the following    TestInitialize  public void Init                 Inside this method it calls a library  which i have no control over  which tries to run the following code   HttpContext Current User Identity IsAuthenticated   Now you can probably see the problem   I have set the fake HttpContext against the controller but not in this base Init method   Unit testing   mocking is very new to me so I want to make sure I get this right   What is the correct way for me to Mock out the HttpContext so that it is shared across my controller and any libraries which are called in my Init method

User · Answer

Below Test Init will also do the job     TestInitialize  public void TestInit       HttpContext Current   new HttpContext new HttpRequest null   http   tempuri org   null   new HttpResponse null      YourControllerToBeTestedController   GetYourToBeTestedController

User · Answer

I know this is an older subject  however Mocking a MVC application for unit tests is something we do on very regular basis   I just wanted to add my experiences Mocking a MVC 3 application using Moq 4 after upgrading to Visual Studio 2013  None of the unit tests were working in debug mode and the HttpContext was showing  could not evaluate expression  when trying to peek at the variables   Turns out visual studio 2013 has issues evaluating some objects  To get debugging mocked web applications working again  I had to check the  Use Managed Compatibility Mode  in Tools  Options  Debugging  General settings   I generally do something like this   public static class FakeHttpContext       public static void SetFakeContext this Controller controller                 var httpContext   MakeFakeContext            ControllerContext context           new ControllerContext          new RequestContext httpContext          new RouteData     controller           controller ControllerContext   context              private static HttpContextBase MakeFakeContext                 var context   new Mock lt HttpContextBase gt             var request   new Mock lt HttpRequestBase gt             var response   new Mock lt HttpResponseBase gt             var session   new Mock lt HttpSessionStateBase gt             var server   new Mock lt HttpServerUtilityBase gt             var user   new Mock lt IPrincipal gt             var identity   new Mock lt IIdentity gt              context Setup c  gt  c Request  Returns request Object           context Setup c  gt  c Response  Returns response Object           context Setup c  gt  c Session  Returns session Object           context Setup c  gt  c Server  Returns server Object           context Setup c  gt  c User  Returns user Object           user Setup c  gt  c Identity  Returns identity Object           identity Setup i   gt  i IsAuthenticated  Returns true           identity Setup i   gt  i Name  Returns  admin             return context Object              And initiating the context like this  FakeHttpContext SetFakeContext moController     And calling the Method in the controller straight forward  long lReportStatusID   -1  var result   moController CancelReport lReportStatusID

User · Answer

If your application third party redirect internally  so it is better to mock HttpContext in below way    HttpWorkerRequest initWorkerRequest   new SimpleWorkerRequest             new StringWriter CultureInfo InvariantCulture    System Web HttpContext Current   new HttpContext initWorkerRequest   System Web HttpContext Current Request Browser   new HttpBrowserCapabilities    System Web HttpContext Current Request Browser Capabilities   new Dictionary lt string  string gt       requiresPostRedirectionHandling    false

User · Answer

HttpContext Current returns an instance of System Web HttpContext  which does not extend System Web HttpContextBase  HttpContextBase was added later to address HttpContext being difficult to mock  The two classes are basically unrelated  HttpContextWrapper is used as an adapter between them    Fortunately  HttpContext itself is fakeable just enough for you do replace the IPrincipal  User  and IIdentity   The following code runs as expected  even in a console application   HttpContext Current   new HttpContext      new HttpRequest      http   tempuri org            new HttpResponse new StringWriter               User is logged in HttpContext Current User   new GenericPrincipal      new GenericIdentity  username        new string 0             User is logged out HttpContext Current User   new GenericPrincipal      new GenericIdentity String Empty       new string 0

[c#] Mock HttpContext.Current in Test Init Method

Examples related to c#

Examples related to unit-testing

Examples related to mocking

Examples related to httpcontext