title: How to implement TDD and Integration Testing, without Repository model, on ASP.Net MVC
body: <p>Our group is just starting out on TDD and Unit Testing. We've started down the path of the Repository Model, and are dubious. It seems to only test small sections of code while requiring a great amount of coding time. We also find that the greatly increased complexity is harder to support. When coupled with the fact that so much business logic, that in SQL, or in the UI layer, is left without coverage and requires even more complexity to cover that code, ....it seems like such a waste of time.</p>
  
  <p>Don't get me wrong, I want to implement TDD, but I want a complete solution that tests from UI to DB. Yes I know that this is called Integration Testing, and I really don't understand why some are so eager to point out that IT is greatly different from UT, that's obvious. But why would you choose UT, bring so much complexity, and getting so little coverage in return for your effort.</p>
  
  <p>What ways have you implemented TDD, using integration testing?</p>