flux88.com — This mess of nastiness is what is required to test your routes in ASP.NET MVC. There are a number of things wrong with this. First and foremost, we're doing magical-mocking here. That is - we somehow know exactly the two properties we need to mock for this to work. It turns out this isn't such a magical process as it is looking at reflector and a lot of trial and error. The next thing wrong that I see is that our route values (and keys) are case-insensitive, so we'd need to include some more flexibility in our Asserts here.
original link