Preferred Method of Disabling SQLCop Tests

JackAceJackAce Posts: 75
edited May 15, 2014 5:35PM in SQL Test
There are a few SQLCop tests that aren't relevant to our local or test environments.

What is the preferred method for disabling these SQLCop tests? Just delete them? Add a RETURN statement in the proc?

My preference is to *not* delete the stored procedures, because I'm sure they'll pop up again if I ever need to reinstall/update the tSQLt framework on the database. I also don't want to go through the headache of deleting them every time I install the framework on another database.

It would be nice to specify a list of tests to exclude when you run tSQLt.RunAll so you could just update your build scripts and you'd at least have some documentation on what you've decided to ignore.


Sign In or Register to comment.