title: How to best create a test DB when doing TDD?
body: <p>what's the best practice for creating test persistence layers when doing an ASP.NET site (eg. ASP.NET MVC site)?</p>
  
  <p>Many examples I've seen use Moq (or another mocking framework) in the unit test project, but I want to, like .. moq out my persistence layer so that my website shows data and stuff, but it's not coming from a database. I want to do that last. All the mocking stuff I've seen only exists in unit tests.</p>
  
  <p>What practices do people do when they want to (stub?) fake out a persistence layer for quick and fast development? I use Dependency Injection to handle it and have some hard coded results for my persistence layer (which is really manual and boring).</p>
  
  <p>What are other people doing? Examples and links would be awesome :)</p>
  
  <h2>UPDATE</h2>
  
  <p>Just a little update: so far I'm getting a fair bit of mileage out of having a fake repository and a SQL repository - where each class implements an interface. Then, using DI (I'm using StructureMap), I can switch between my fake repository or the SQL repository. So far, it's working well :)</p>
  
  <p>(also scary to think that I asked this question nearly 11 months ago, from when I'm editing this, right now!)</p>