It can be challenging to add unit testing to a project that was built without planning to incorporate it. The ASP.Net MVC Music Store tutorial was not built with unit testing in mind, but today we're going to walk through the addition of Controller unit tests, focusing on a controller that directly references Entity Framework objects and implicitly interacts with ASP.Net Membership objects and Request data from the current HttpContext.

I was not really convinced in the past that I should use the Structuremap Automocker for any of my tests. I don't like using the container in my tests it makes them way to dependent on something not really needed to run the test. Of course I test to see if the container is well configured and if the objects are created by the container when it is well configured (this has saved me several times before). I really only have myself to blame because I didn't really try it and only suspected what it was doing.

Well apparently I was wrong, and lucky for me I read the right blogs.