Sometimes, it seems just too complicated or expensive to test-drive a certain component in an ASP.NET MVC context, or it would require the use of some browser automation framework. To make testing easier in such cases, this post introduces a Gallio/MbUnit test fixture that builds on top of a framework for integration testing ASP.NET MVC applications without the need for any browser or server, but still running in the real (non-mocked) ASP.NET runtime...
This post shows how an application's LinFu Ioc container can be seamlessly integrated with the ASP.NET MVC framework, enabling Dependency injection and the use of interfaces for controller creation and for viewmodels (both in controllers and views)...
This is a follow-up on my series about validating business objects throughout different layers of a software system - domain, persistence, and (ASP.NET MVC) GUI. It demonstrates how a self-written validation can be incorporated into a web page (using a bit of JavaScript) and how this can be mapped to a custom validation on the domain side...
This is the third post of a three-part series that discusses the use of the ValidationAspects aspect library for business object validation and its integration in different application layers. This time the (server-side) validation aspects are "translated" to (client-side) validations of ASP.NET MVC application web pages, using the xVal framework to do the mapping...
Sometimes, unit testing/test-driving a certain piece of code is very painful and complicated, because the respective component has lots of dependencies. In such a case we usually decide not to unit test the respective component, simply because it wouldn't pay. The route table in an ASP.NET MVC application is such a component. To help with that, this post presents an easy-to-use base class for a test fixture targeting an ASP.NET MVC application's route table...