Comments
3 comments
-
Hi,
I believe one of our guys have addressed this question on Stack:
http://stackoverflow.com/questions/2110 ... ntegration
I hope the answer is helpful. -
Our TeamCity plugin is currently limited to a tSQLt.RunAll under the hood, so if you want to run only a specific class for now you'll need to create your own custom steps. Dave Green's article explains how you might go about settings this up.
http://d-a-green.blogspot.co.uk/2012/07 ... t-red.html -
@BDonahue - thanks for the ref. But that's actually my stack post and it was somewhat helpful ... ;-)
Add comment
Please sign in to leave a comment.
I am using SQL Test to create some unit tests in SQL Server. And I integrated with Teamcity so that on a build, it auto runs the tSQLt tests.
The issue is that we plan to create hundreds of unit tests for all our store procs. And we don't want to run all of the unit tests each time we check in code and whereby Teamcity runs a build + runs the unit tests.
What I am wondering is if there is a way to configure the integration build to only run unit tests for new tests that are checked in.
Or is the practical solution to check in without Teamcity auto running the tSQLt unit tests? Thereby, just manually run the new test cases on the DEV server (after check in)? An extension of this is to run a batch nightly to run ALL the unit tests.