Back in the mid-noughties I decided to see if I could write SQL in a test-first manner (i.e. TDD). This resulted in me writing a 100% T-SQL based unit testing f

Back in the mid-noughties I decided to see if I could write SQL in a test-first manner (i.e. TDD). This resulted in me writing a 100% T-SQL based unit testing framework for SQL Server [1] which we then used for the SQL back-end at an investment bank. On the back on that professional use I wrote a blog post [2] explaining why you might choose to go down this route as it wasn't the way database was developed way back then (SQL wasn't developed in the same way as the other front-end and back-end code). A few years later I gave a short 20-minute talk (videoed) to show what writing SQL using TDD looked like for me. It's hard to show all the kinds of tests we wrote in practice at the bank but the talk is intended to show how rapid the feedback loop can be using a standard DB query tool and two code windows - production code and tests. Be kind, it was a long time ago and I'm sure the state of the art has improved a lot in the intervening years :o). Chris Oldwood --- [1] SQL Server Unit: https://github.com/chrisoldwood/SS-Unit https://github.com/chrisoldwood/SS-Unit [2] You Write Your SQL Unit Tests in SQL?: https://chrisoldwood.blogspot.com/2011/04/you-write-your-sql-unit-tests-in-sql.html https://chrisoldwood.blogspot.com/2011/04/you-write-your-sql... [3] Test-Driven SQL: https://www.youtube.com/watch?v=5-MWYKLM3r0 https://www.youtube.com/watch?v=5-MWYKLM3r0