+1 This is what we found on our last project too, we had to mock a whole bunch of stuff to test controllers when most of the work was happening in other places, essentially these tests become redundant tests of your infrastructure. We had a suite of automated UI tests too which gave us good coverage of the controller actions.
Damian On Tue, May 18, 2010 at 1:20 AM, Davy J <[email protected]> wrote: > When we did the MVC app at the end of last year we tried to implement TDD > on the (c) controler part of mvc, but we realised pretty quickly that we > wern't actually testing anything. In the end we tested the business logic, > the database connections and then used Selenium (firefox plugin) to test the > controlers via web interface (http://buildmachine/MVCApplication/Books/32) > > Davy. > >
