Strange issue with SQL Test on the build server
Ron_Verhees
Posts: 5 New member
in SQL Test
Hi,
We're seeing a strange issue with Redgate SQL Test in combination with our build server (TFS) and the Redgate SQL Change control components.
In SQL Test we have a bunch of test cases added to all of our databases. We store all of these tests in 1 database and use SQL compare whenever a new test case is added to deploy all test cases to all of our databases to keep the test cases in sync. This works perfectly.
Because not all databases have to pass all of the tests, we added a control table to each database where we can list all of the tests we do not want to test. All test cases have been updated to look at this control table and if it finds the test name, it will just pass the test without any further checks, if it doesn't find it, it'll run the test case. The control table is linked as static data to source control so it's available on the build server too.
This all works fine on the developers local machines, but when checking-in the code and running the test using the redgate TFS component all the tests execute as normal so the tests fail.
Any idea why this is happening? It's almost like it's not querying the control table for some reason?
Thanks,
Ron
We're seeing a strange issue with Redgate SQL Test in combination with our build server (TFS) and the Redgate SQL Change control components.
In SQL Test we have a bunch of test cases added to all of our databases. We store all of these tests in 1 database and use SQL compare whenever a new test case is added to deploy all test cases to all of our databases to keep the test cases in sync. This works perfectly.
Because not all databases have to pass all of the tests, we added a control table to each database where we can list all of the tests we do not want to test. All test cases have been updated to look at this control table and if it finds the test name, it will just pass the test without any further checks, if it doesn't find it, it'll run the test case. The control table is linked as static data to source control so it's available on the build server too.
This all works fine on the developers local machines, but when checking-in the code and running the test using the redgate TFS component all the tests execute as normal so the tests fail.
Any idea why this is happening? It's almost like it's not querying the control table for some reason?
Thanks,
Ron
Tagged:
Best Answer
-
Ron_Verhees Posts: 5 New memberthanks for the reply Sergio, we actually figured out the issue since... we had the box ticked where it was generating test data in all tables and this actually overwrites any static data (in our case in our test control table). Once we unticked this all was working as expected.
Answers
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools