Comments
Sort by recent activity
Thanks, we're still seeing this behavior. / comments
Thanks, we're still seeing this behavior.
mfearby - Our shop commits tSQLt objects and developer written tests with our source control. We apply the filters when deploying to non-testing environments, so they won't eventually make it to production.
You need those objects (the tSQLt objects as well as your own) there if you want to run the unit tests, so it makes sense that you would always want one with the other. / comments
mfearby - Our shop commits tSQLt objects and developer written tests with our source control. We apply the filters when deploying to non-testing environments, so they won't eventually make it to p...
Looks like it may be related to this thread?
SQL Test is over a year behind tSQLt: http://www.red-gate.com/MessageBoard/vi ... hp?t=18049 / comments
Looks like it may be related to this thread?
SQL Test is over a year behind tSQLt:http://www.red-gate.com/MessageBoard/vi ... hp?t=18049
I'm currently using SQL Test 1.5, but the tSQLt framework may have been installed with an earlier version of SQL Test.
I've uninstalled and reinstalled the framework. The objects show up now. Thanks. / comments
I'm currently using SQL Test 1.5, but the tSQLt framework may have been installed with an earlier version of SQL Test.
I've uninstalled and reinstalled the framework. The objects show up now. Tha...
I'm still experiencing this and I just updated SQL Source Control to version 3.6.0.3 on a brand new machine. / comments
I'm still experiencing this and I just updated SQL Source Control to version 3.6.0.3 on a brand new machine.
We'll probably wait until 10.5 is available with all migration issues resolved. Is there an ETA on when it will be released again? / comments
We'll probably wait until 10.5 is available with all migration issues resolved. Is there an ETA on when it will be released again?
FYI - As a work around, we have been specifying IgnoreWithNocheck, but this is not ideal. / comments
FYI - As a work around, we have been specifying IgnoreWithNocheck, but this is not ideal.
David Atkinson wrote:
Yes, this is possible as tSQLt can output an Ant JUnit XML Report, which can be consumed by CI tools. Rather than describe it here, I'll direct you to Dave Green's excellent article: http://www.simple-talk.com/sql/sql-tool ... tegration/
Thanks, David. I've amended my scripts. / comments
David Atkinson wrote:
Yes, this is possible as tSQLt can output an Ant JUnit XML Report, which can be consumed by CI tools. Rather than describe it here, I'll direct you to Dave Green's excellen...
In case anyone else was wondering, I found the solution to the build failure problem. You can cause sqlcmd.exe to fail if you use the -b option <Target Name="Test">
<Message Text="==================================================" />
<Message Text="== Run tSQLt Tests" />
<Message Text="==" />
<Exec Command=""$(SqlCmdPath)" -Q "EXEC tSQLt.RunAll" -S localhost -d MyDb -b -E" />
<Message Text="==================================================" />
</Target>
/ comments
In case anyone else was wondering, I found the solution to the build failure problem. You can cause sqlcmd.exe to fail if you use the -b option <Target Name="Test">
<Message Text...
You're right, we are using SQL Data Compare to deploy. We are using SQL Data Compare version 9.0.0.117.
We definitely unlinked the tables via Red Gate SQL Source Control. There is no longer a MyTable_Data.sql file in the Data folder, but the information still exists (and keeps getting repopulated) in the RedGateDatabaseInfo.xml file.
The schema of this table hasn't been touched for a while. / comments
You're right, we are using SQL Data Compare to deploy. We are using SQL Data Compare version 9.0.0.117.
We definitely unlinked the tables via Red Gate SQL Source Control. There is no longer a MyT...