Easy unit testing for databases in SQL Server Management Studio
Moderators: JonathanWatts, David Atkinson, Anu Deshpande, Michelle Taylor, David Priddle
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.
- Posts: 45
- Joined: Fri Jul 08, 2011 11:00 pm
Unfortunately, there's no direct way to disable the SQL Cop tests. This would be a good feature request for the tool, and here's the forum for you to do so: http://sqltest.uservoice.com/forums/140 ... test-forum
There is a manual workaround that you can do in the meantime. You can export a copy of the test from SSMS and save the script, and then re-add as needed.
Red Gate Product Support
- Site Admin
- Posts: 8
- Joined: Thu May 15, 2014 10:24 pm
Return to SQL Test
Who is online
Users browsing this forum: No registered users and 0 guests