ReadyRoll 1

Tutorial: Running tests in ReadyRoll with tSQLt Adapter


This tutorial helps you get started with running tSQLt tests in ReadyRoll. It uses AdventureWorks.Database as a sample ReadyRoll project, but the steps are applicable to any ReadyRoll project.

As this tutorial requires the use of Programmable Objects, it will not work with ReadyRoll Core edition.

Set up test project

Create a new project

In Visual Studio in your AdventureWorks.Database solution, select New Project from the File menu and create a new ReadyRoll SQL Server Database Project named AdventureWorks.Database.Tests. Do not connect this project to any database at this point.

Switch on Programmable Objects

In the Solution Explorer, right-click the AdventureWorks.Database.Tests project and select Properties. In the Programmable Objects section, select Import into separate script files.

Add a build dependency

Right-click the AdventureWorks.Database.Tests project in the Solution Explorer. Open Project Dependencies using Build Dependencies > Project Dependencies... and select AdventureWorks.Database to add the dependency.

Right-click the References node for the AdventureWorks.Database.Tests project and select Add Database Reference. Select the AdventureWorks.Database project as the Database Reference. Select Same database as the Database location. Click OK to add the reference.

Set the target database

In the Solution Explorer, right-click the AdventureWorks.Database.Tests project and select Properties. Select Debug tab from the panel on the left and in the Target Connection String section click on the Edit... button. This will open a connection dialog. In this dialog, select the database that the AdventureWorks.Database project is connected to.

The test project has to point at the AdventureWorks.Database target database, as there is no database in AdventureWorks.Database.Test.

Ignore tSQLt in the database project.

Unload the AdventureWorks.Database project by going to the Project menu and click Unload Project. In Solution Explorer, right-click the unloaded project and click Edit AdventureWorks.Database.sqlproj. In AdventureWorks.Database.sqlproj, edit the SyncOptionIgnoretSQLt property to:


Save the file and reload the project using Project > Reload Project.

Change the migration log schema name for the test project.

Unload the AdventureWorks.Database.Tests project by going to the Project menu and click Unload Project. In Solution Explorer, right-click the unloaded project and click Edit AdventureWorks.Database.Tests.sqlproj. In AdventureWorks.Database.Tests.sqlproj, add a custom migration log schema name that is different to the schema name in AdventureWorks.Database (default is dbo):


Save the file and reload the project using Project > Reload Project.

Write your first tSQLt test

Install the framework

In your AdventureWorks.Database.Tests, in the Migrations folder add a new script and rename it to 0001_Install_tSQLt.sql. Download the Setup script and copy the contents of tSQLt.class.sql into 0001_Install_tSQLt.sql, making sure you leave the Migration ID on the first line.

Use tSQLt Visual Studio Test Adapter

Download and install the test adapter.

Create an AdventureWorks.runsettings file in the solution root with the following content:

<?xml version="1.0" encoding="utf-8"?>
    <Parameter name="TestDatabaseConnectionString" value="Data Source=(localdb)\ProjectsV13;Initial Catalog=AdventureWorks.Database;Integrated Security=True;" />
    <Parameter name="IncludePath" value="Tests" />

The value of TestDatabaseConnectionString needs to match Properties > Debug > Target Connection String in AdventureWorks.Database.

Select the file by going to Test > Test Settings > Select Settings File (This option is sometimes disabled. Go to Test > Run > All Tests, to enable it.)

Write a sample test

Right-click the AdventureWorks.Database.Test project and select Add > Inline function... This will create a new function in the Programmable Objects folder, where you can write your test e.g.

-- <Migration ID="565a2147-9a0d-4e91-8494-1306ca209e6f" />
EXEC tSQLt.NewTestClass 'ufnGetAccountingEndDateTests';

CREATE PROCEDURE ufnGetAccountingEndDateTests.[test that correct accounting end date is returned]
    SELECT @actual = [dbo].ufnGetAccountingEndDate();

    DECLARE @expected DATETIME;
    SET @expected = '2004-06-30 23:59:59:998';
    EXEC tSQLt.AssertEquals @expected, @actual;

Run the tests

In the Test menu, select Run > All tests.

The test results are displayed:

Find out more about writing tSQLt tests.


Didn't find what you were looking for?