Q:

Does System.Web.HttpServer perform well for ASP.Net WebAPI unit testing?

I have been looking at unit testing a ASP.Net WebAPI project. I can obviously test controller Get methods easily in terms of the data it returns however I was looking at testing things like headers.
I have used NancyFX before and this provides a nice clean testing capability that returns a proper HTTP response even though no client/server has been setup.
The alternative I can see in WebAPI is to use HttpServer and HttpConfiguration to run a server in-memory.
If I do this I was wondering if someone knew what the performance of it is. If its not that great then it becomes an integration test unfortunately.
Simple scenario, I want to test the response header content type. Without the in-memory configuration I'm not sure how you test that in WebAPI

A:

I am running 80 tests in under 1 second. I think performance is adequate.  
Note: if you don't host your api tests in the same project as the controllers themselves you will need to override the controller creation. I do this usinga  StructureMap dependency resolver which also implements the IHttpControllerActivatorinterface so controllers are resovled from the container rather than the default activator.

