Answer by Grant Fritchey
We don't do it as much as we did, but my group went through a period where we were following test driven development within TSQL. We were using the SQL specific test suite, the name escapes me at the...
View ArticleAnswer by jjerome
Yes, we use and find it extremely useful.In our case, we are a (very) small team that supports a database that is vital to company business. Our code base is pretty complicated for what it is (C++ on...
View ArticleAnswer by Tim Edlund
Our group has been doing unit testing on backend objects for about 2 years now. We require at least one unit test on each simple database object and on stored procedures the objective is to excercise...
View ArticleAnswer by Fatal Exception Error
Yes. Invaluable for finding bugs before they hit QA.A must for making sure changes done do not affect the next tier due to the complexity of some stored procs and legacy systems being converted.
View ArticleAnswer by PeterMarriott
Yes, we Unit Test some of the more complex stored procedures. We use dbFit based on the Fitnesse platform. http://www.fitnesse.info/dbfit It has been invaluable when refactoring complex sps. One sp...
View ArticleAnswer by TimothyAWiseman
Yes, though sometimes indirectly. Generally, I rely on the unit tests for the procedures in my main code base that calls on the stored procedure. For stored procedures that are custom written for the...
View ArticleAnswer by xiaoyuandlg
You may take a read for some [Code UI control][1]. [1]: http://www.kettic.com/winforms_ui/ui_test.shtml
View Article