It is phooey that testing is new to database developers.

There is a bit of envy to be had from some of the testing frameworks for the OOP world. However, it is really important to realize that database developers face different challenges. Testing a deterministic scalar UDF is a piece of cake not even really needing a test harness. Although there are a test harnes does allow for automation and should net be ignored. However, testing a stored procedure with set based inputs and artifacts is a bit more complicated. I'm open to suggestions on real sample data and ddl management techniques for database developers. This is a conversation worth spending some time on. Taking testing techniques up to new levels of quality and simplicity is a worthy goal.

Some colleagues from the Philadelphia SQL Server Users Group, PSSUG, put together a solution that is worth looking at.

http://www.sqlity.net/sqlity/articles/tSQLtTutorial

{boy are they going to be surprised at the traffic}

It was interesting to discuss the various solutions and techniques for implementing a TDD solution in SQL server. For Example, to use transactions and roll backs vs automated stubbing of data structures.