Before the database world can get how it manages releases straight, it has to get its technical house in order by following the same path that "regular programmers" started on long ago. One of the key activities that must be ported into the database world is test-driven development.
Without test-driven development (TDD), there can be no agility and a software product is doomed to descend into an endless cycle of defect introduction and remediation. With TDD, on the other hand, a product can be driven in the other direction-releasing faster and faster with fewer and fewer defects over time.
Test-driven development, however, is not just some practice that you can copy over to your database development process unmodified. It is a discipline, a collection of forces and wisdom. Essentially: it is a pattern for software development behavior. It needs to be instantiated in the context of database development in order to produce its full effect.
This book does just that: it shows you one way to do true TDD in the context of database development, taking into account the parts that are the same as traditional object-oriented development and the parts that are different.What do you think?
Also: Shame on you if you don't get the reference in the link title.
