Unit testing routing in ASP.NET Core 1.0 (ex MVC 6)

Question

As the architecture of ASP.NET Core 1.0 (ex MVC 6 / ASP.NET 5.0) changed significantly, how would one go about unit testing the routing?

As an example, I like the libraries such as this one (as for <= MVC 5): https://github.com/AnthonySteele/MvcRouteTester

Something down the lines of fluent extension methods:

routes.ShouldMap("/").To<HomeController>(x => x.Index()); 

Answer 1

Alright... I did ping the ASP.NET team and asked them how they proceeded to do their tests.

Short answer

You can't unit test without mocking the world. You have to do integration/functional tests.

Slightly longer answer

Routing can come from many places (attributes, pre-defined routes, areas, etc) and can even be altered by middleware. Including all those scenarios in a test would need to setup some massive dependency tree while there is an easier way to test it.

How they do it.

• Startup.cs
• RoutingTests.cs
• TestResponseGenerator.cs

Basically, they are creating a TestStartup.cs, self-hosting the app in the test process and hitting itself to see how it behaves. They override the results and... that's pretty much it.

I think I've given you all the possible tools here to actually bootstrap something for yourself.