Chris Harshman (7/25/2016)
Where I work, the developers do a lot of test driven development for their C# work, but a limiting factor for them doing more on the database side is the tools available. They evaluated some methods, and tried tSQLt for a while, but had more problems with it than problems that it solved.
I'd be curious what were the failings. There are holes and issues, but it's helpful. Part of the trick is learning how to write tests that work in your situation.
There's the MS Unit Testing framework that works as well, allowing for SQL Server tests.