This document discusses unit testing ASP.Net and ASP.Net MVC applications. It notes that ASP.Net applications are difficult to test because they rely on server state like HttpContext. Testing through a browser is slow and hard to debug. However, ASP.Net MVC is more test-friendly as it works through interfaces and BaseHttpContext, but still has challenges like testing redirection and custom code. The document provides examples of testing what is written to the client, an MVC controller, and security logging. It promotes downloading Isolator.Net and Ivonna for isolation testing and concludes by calling the audience to action.