How can we improve SQL Test?

Need a way to easily disable tests

There are tests (especially SQLCop tests) that I'd like to be able to disable easily so they don't automatically get run when you execute tSQLt.RunAll.

I don't want to delete the test, because there's value in knowing the test exists. You may not be able to fix *all* SQLCop issues right away, but you don't want the build to fail until you have time to fix it. There may be a user story to fix the issue, and you'd like to disable the test until the issue is fixed.

You should be able to disable the test by either
* Passing in a list of test names to ignore when calling tSQLt.RunAll or...
* By adding some Extended Property to the test that flags it as disabled or...
* There should be an internal tSQLt table that stores a list of tests to be ignored (my preferred solution)

I realize that addressing this issue might be more of a tSQLt feature request, but I'm still submitting this request here.

14 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Anonymous shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base