Test-Driving ASP.NET MVC

At the core of the Model-View-Controller (MVC) pattern is the segregation of UI functions into three components. The model represents the data and behavior of your domain. The view manages the display of the model and handles interactions with users. The controller orchestrates the interactions between the view and the model. This separation of inherently difficult-to-test UI logic from the business logic makes applications implemented with the MVC pattern extremely testable. In this article I’ll discuss best practices and techniques for enhancing the testability of your ASP.NET MVC applications, including how to structure your solution, architecting your code to handle the injection of dependencies and implementing dependency injection with StructureMap.