Last week I explained how to configure a CI build for your SQL Server Database project. This week we’ll continue by adding Unit testing into the mix.
Before we can run our test, we need to have one. So let’s start by adding a unit test to your database project. One way to do this is to click on a stored procedure, function,etc… and choose Create Unit Tests…
On the Create Unit Tests screen, specify the Test project you want to use(or create a new one), choose a good class name and click OK.
Before we run our database test, we’ll have to specify which database we’ll use. Therefore right click on your test project and choose SQL Server Test Configuration…
Choose the database where you want to run your test. Optionally you can specify a different connection string(using different credentials) to run the test validations.
This is enough to run your tests locally, but if you want to integrate them into your CI build, we’ll have some extra work to do. First of all, we need to add an extra line to set the VisualStudioVersion environment variable in our test code. If we don’t do this MSBuild will try to use the v11.0 tools and fail to deploy since they aren’t installed on our build controller.
We also have to do the same thing inside our build definition. So let’s open up our Build Definition again and add an extra build parameter: /p:VisualStudioVersion=12.0
That’s it! Time to check-in all our changes, and see how our build (hopefully) turns green again…
