Unit Testing ASP.NET Web API

Question

I'm unit testing a simple post:

public HttpResponseMessage<Document> PostDocument(Document document) 
{
    document = repository.Add(document); 

    var response = new HttpResponseMessage<Document>(document, HttpStatusCode.Created); 

    var uri = Url.Route(null, new { id = document.Id }); 

    response.Headers.Location = new Uri(Request.RequestUri, uri); 

    return response; 
}

However, the 'URL' and 'Request' are obviously going to be null.

Is there an alternative to mocking out ControllerContext and HttpContext?

Update:

Changed it to:

 public HttpResponseMessage<Document> PostDocument(Document document,Uri location = null) 
{
    document = repository.Add(document); 

    var response = new HttpResponseMessage<Document>(document, HttpStatusCode.Created);

    if (location == null)
    {
        var uri = Url.Route(null, new { id = document.Id });
        location = new Uri(Request.RequestUri, uri);
    }

    response.Headers.Location = location;

    return response; 
}

Update 2:

This is better:

public HttpResponseMessage<Document> PostDocument(Document document)
{
    var uri = Url.Route(null, new { id = document.Id });
    var location = new Uri(Request.RequestUri, uri);

    return PostDocument(document, location);
}

[NonAction]
public HttpResponseMessage<Document> PostDocument(Document document, Uri location) 
{
    document = repository.Add(document); 

    var response = new HttpResponseMessage<Document>(document, HttpStatusCode.Created);
    response.Headers.Location = location;
    return response; 
}

related: http://stackoverflow.com/questions/10042290/sample-code-for-unit-testing-api-controllers/22200520#22200520 — Ruben Bartelink, Mar 06 '14 at 10:06

score 1 · Answer 1 · answered Jan 16 '13 at 21:33

1

Using FakeItEasy I got it to work doing this in the TestInitialize.

this.Controller.ControllerContext = new System.Web.Http.Controllers.HttpControllerContext();
this.Controller.Request = A.Fake<HttpRequestMessage>();

answered Jan 16 '13 at 21:33

AlignedDev

8,102
9
56
91

score 1 · Answer 2 · answered Feb 28 '12 at 16:22

1

The Request property should be settable, so you only have to set the ControllerContext (which should have a no-arg constructor so you shouldn't even have to mock).

answered Feb 28 '12 at 16:22

marcind

52,944
13
125
111

score 0 · Answer 3 · answered Mar 20 '12 at 16:11

Your method might recieve HttpRequestMessage as parameter.

 public HttpResponseMessage<Document> PostDocument(Document document, HttpRequestMessage message)
{

}

You can take RequestUri from it. In your unit tests you can put test double of HttpRequestMessage object.

Unit Testing ASP.NET Web API

3 Answers3

Linked