Comments
2 comments
-
Hi @Iam_mrad
Would you be able to provide your SQL Change Automation project, as well as a dbcc clone of your database you used for the baseline?
https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-clonedatabase-transact-sql?view=sql-server-ver15
You can create a ticket with support if you don't want to share this information on the forum:
https://productsupport.red-gate.com/hc/en-us/requests/new
-
Running tSQLt tests in Azure CI/CD can streamline your database testing process significantly. I've found that integrating these tests into the pipeline not only improves code quality but also enhances team collaboration. It reminds me of the time I took an iq test free to gauge my analytical skills; it’s all about ensuring everything is functioning as expected. Setting up the tests in Azure DevOps is straightforward, and the benefits are well worth the effort!
Add comment
Please sign in to leave a comment.
I have a SCA project with some tests in tSQLt framework,
but I don't want to deploy tests to production environment,
so I create two SCA projects, first one only contains business schemas and the second one only contains tSQLt and test schemas, that both of them base on same database,
I thought i could deploy first project in azure and then apply test project on it and run tests,
for that assumption i used two "SQL Change Automation: Build" tasks in azure build pipeline,
the first one work good,
but the second one, drop the first one and create a new database that only has test objects,
I don't know if I'm on the right track or not?
and now how can i continue?