ASP .NET Web API controller testing

Question

I'd like to unit test some controller actions and ultimately test that validation attributes and action response filters are functioning properly. To do this sort of thing in ASP .NET MVC was easy with mvccontrib; however, with Web API, mocking the HttpContext seems to be quite a bit different.

How do I go about mocking HttpContext for a Web API controller so that I can test model binding and the like?

Darrel Miller · Accepted Answer · 2012-06-07 02:54:53Z

2

You shouldn't need HttpContext in a Web API. Everything you need should be in the HttpRequestMessage and its Properties collection.

answered Jun 7, 2012 at 2:54

Darrel Miller

143k32 gold badges202 silver badges246 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Scotty.NET Over a year ago

What about application settings in HttpContext.Current.Application?

Darrel Miller Over a year ago

@Scotty.NET Use request.Properties to store whatever state you need to store. If you need stuff global state in there, then create a message handler to store the state and add it to the properties collection on each request.

Scotty.NET Over a year ago

You have confirmed what I was thinking would be the case. Thanks for that.

user20108629 · Accepted Answer · 2022-10-26 09:22:31Z

0

Do not use HttpContext. Just Mock the service and the controller and go with somthing like this:

_serviceMock.Setup(s => s.YourFunction(params if needed)).Returns(return value).
var response = _controllerMock.YourFunction(parameter);
_serviceMock.VerifyAll();
var result = response.Result;
var value = result.Value;

answered Oct 26, 2022 at 9:22

user20108629

Collectives™ on Stack Overflow

ASP .NET Web API controller testing

2 Answers 2

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related