Hi

We are using the Owin Test Server in our codebase to run boundary tests against our API instance. We have the following line of code within a fixture, and the fixture is used across multiple tests. The tests are written using XBehave, which is backed by XUnit 2.



The Startup.cs is from our API project. This subsequently registers the routes, which causes the following exception:



Every single API test fails that uses this fixture, across 9 different test classes.

If I make the Server variable static within the fixture then this problem goes away, however everything I have read makes me feel this shouldn't even be happening?

Can someone give me some guidance about what might be causing this issue?

Cheers
Ant

Hi Remco

Thanks for getting back to me. Your response pointed me to the right direction. The cause is the reuse of the test runner process across tests.

The Startup class had a static call to RouteTable.Routes. I introduce a new derived class from Startup and made the call to get the routes a virtual method, returning RouteTable.Routes in the Startup class, and a new RouteCollection in my TestStartup class when any routes were found. This is because the presence of any routes meant the static config had already been set up.

The result is code introduced just for NCrunch, but its footprint is lightweight and it's an acceptable pattern to my mind.