how to unittest an asp.net web api?

Question

I never did unittesting for an asp.net web api. The service is about posting a JSON in the request and returning a JSON result after JSON schemavalidation and querying. Just wondering how to unittest a web api in general. An example of a test would be posting an invalid JSON string and testing whether this returns the correct HTTPcode ie 400 or something. This is roughly what my service looks like:

public class MyApiController : ApiController
{
   public HttpResponseMessage Post([FromBody]dynamic value)
   {
      return response;
   }
}

Also how can I use constructor injection with web apis? If I use a constructor here my value that is posted is null?

The official ASP.NET Web API site has an introduction that seems to be written for people who've never tried it before: asp.net/web-api/overview/testing-and-debugging/… — Mark Seemann
– Mark Seemann, Commented Mar 25, 2014 at 8:53
Related: How to Integration Test ASP.NET Web API: stackoverflow.com/a/22294059/126014 — Mark Seemann
– Mark Seemann, Commented Mar 25, 2014 at 13:21

petchirajan · Accepted Answer · 2014-03-25 08:54:15Z

1

You can directly create the instance of controller. If you are used any complicated code, you can create mock for the class for unit testing. Refer this link to understand unit testing of ASP.NET web API.

answered Mar 25, 2014 at 8:54

petchirajan

4,3601 gold badge20 silver badges21 bronze badges

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

Comments

unarity · Accepted Answer · 2014-03-25 08:58:04Z

0

[Test]
    public async void GetSettingsRequest()
    {
        var getSettingsResponse = await api.GetSettings();
        Assert.IsNotNull (getSettingsResponse);
        Assert.IsTrue (getSettingsResponse.Success);
        Assert.IsNotNullOrEmpty (getSettingsResponse.Email);
    }

I made test project which is making request on api server. After request is made, wait for response and test response.

answered Mar 25, 2014 at 8:58

unarity

2,4452 gold badges22 silver badges17 bronze badges

Comments

Steven Liekens · Accepted Answer · 2014-03-25 09:03:42Z

My first thought is that you should figure out what you want to test first. That means just jotting down all of the expected behaviors, then writing tests to ensure that your controller behaves as... expected.

Let's start with two fictional test cases:

The response is not null
The response always carries a success status code

--

class MyApiControllerTest
{
    private MyApiController myApiControllerFixture;

    [TestInitialize]
    void Initialize()
    {
        this.myApiControllerFixture = new MyApiController();
    }

    [TestMethod]
    void MyApiController_Post_ResponseNotNullTest()
    {
        var response = this.myApiControllerFixture.Post(new { });

        Assert.IsNotNull(response);
    }

    [TestMethod]
    void MyApiController_Post_SuccessStatusCodeTest()
    {
        var response = this.myApiControllerFixture.Post(new { });

        Assert.IsTrue(response.IsSuccessStatusCode);
    }
}

Just add tests as you discover new required behaviors, and delete obsolete tests when behaviors change.

Collectives™ on Stack Overflow

how to unittest an asp.net web api?

3 Answers 3

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related