Ed Elliott continues to amaze me. This time, he’s got a code coverage tool for T-SQL code:
If we execute this stored procedure we can monitor and show a) how many statements there are in this and also b) which statements have been called but we can’t see which branches of the case statement were actually called. If it was a compiled language like c# where we have a profiler that can alter the assembly etc then we could find out exactly what was called but I personally think knowing which statements are called is way better than having no knowledge of what level of code coverage we have.
Yet another reason to grab the SSDT Dev Pack. By this point, I expect there to be a couple more reasons next week…