Download to read offline
Uploaded byGil Zilberfeld
Unit Testing Asp.net and Asp.net MVC
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.
More Related Content
More from Gil Zilberfeld
Unit Testing Asp.net and Asp.net MVC
- 1. Unit Testing ASP.Netand ASP.Net MVC Gil Zilberfeld 23-Nov-2011
- 2. Agenda • What is different from testing regular apps • The performance hit of testing with a browser • What’s new in MVC that makes it more testable • What still remains in MVC that’s still hard to test • What needs to be tested – logic • Example – testing what’s written to the client • Example – testing an MVC controller • Example – testing for security logging • Example – testing control logic with Ivonna • Call to action – download Isolator.Net and Ivonna
- 3. ASP.Net apps hardto test • Rely on server state • HttpContext and friends • Testing through browser is: • Slow to run • Hard to debug • ASP.Net is not test-friendly • HttpContext and friends
- 4. And MVC? • Moretest-friendly • Works through interfaces • BaseHttpContext • But not completely • For example: Redirection • And your code
- 5.
- 6. Questions? www.typemock.com www.gilzilberfeld.com blog.typemock.com gilz@typemock.com @typemock @gil_zilberfeld