We discussed the basics of test-driven database development (TDDD) with examples and compared it with traditional database development in the first part of this article. In the second part, we are going to move beyond basics to focus on a more realistic scenario of meeting report requirements by using TDDD. A quick recap of TDDD at this point is handy in understanding how it can help us to achieve such goals. Test-driven database development (TDDD) Recap As the name indicates, test-driven database development (TDDD) is a database development method of meeting requirements through unit tests. It is always necessary to implement unit tests before the main database code since they drive the database development as a whole. In other words, database objects (such as "view", "stored procedure", etc.) are necessary to meet the database-related business requirements but they always have to pass the unit test(s) before they are enough appropriate for such purpose. In TDDD, business requirements are encapsulated in database unit tests.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

SQL Server,sql server,ssms,tdd,unit test