Thanks Andy, for posting this article. As a long time fan of TDD and TD3 I found your approach of using SSMS solutions/projects interesting.

Over the years I have worked on data-centric projects and have used SqlUnit, TSQLUnit, dbUnit, etc. These testing frameworks work great for TD3 but require that database developers write tests in XML. Not a big deal, but it can be off-putting for some developers.

On my most recent project I introduced our team to DbFit (http://gojko.net/fitnesse/dbfit/) Gojko Adzic's extension of Fitnesse for database testing. Team members adapted easily to the rhythm of: write a little test; watch it fail; make it pass; make it better; repeat. The DbFit fixtures kept us from having to do the initial "heavy lifting" needed to get our tests running.

Another benefit of database test automation is the ability to run all tests in an automated build (continuous integration) environment. This is another topic that deserves to be introduced to database developers.