SQL Change Automation can be used alongside tSQLt to handle SQL unit testing.

This is done by configuring two SQL Change Automation projects, one for the database objects, and one for the tests, each corresponding to a different set of schemas in the database.

Filters must be configured for the two projects, so that the main project excludes the test schema, and the test project excludes the other schemas.

Additionally the test project must be configured to use a separate schema for its migration log table in its project settings file.

It is also worth noting that there is a SQL Compare option for ignoring tSQLt tests which must be configured correctly for each project.

Learn more

• Using tSQLt in Visual Studio
• Use SQLCover with SQL Change Automation PowerShell cmdlets
• Setting up a project with a companion tSQLt project in SSMS