Entity Framework, Unit Testing and the Repository Pattern

I gave myself a problem. I started reading about test-driven development (TDD), and it had me intrigued. The way I generally developed websites was having the presentation layer of my applications (mainly MVC websites) somewhat tightly coupled with the data source. Controllers would be access the database via L2S or EF and pass the returned model to the view. This works, sometimes (small projects, etc...), but it isn't exactly great when projects start to expand and testing becomes useful.


The Stored Procedures Debate

Having just started a new job where I'll be working on a particular product for some time, I've spent the last couple of days reviewing the code base, documentation and database structure.