How to: Create an Empty SQL Server Unit Test
Include unit tests in your database project to verify changes you make to database objects do not break existing functionality. The following procedures explain how to create SQL Server unit tests for any database object. SQL Server Data Tools includes some additional support for database functions, triggers, and stored procedures. For more information, see How to: Create SQL Server Unit Tests for Functions, Triggers, and Stored Procedures.
When you create a SQL Server unit test using the first procedure, a test project is automatically created for you if no test project exists. If test projects already exist, you have the option of adding the new test to one of those projects or you can create a new test project. For more information about test projects, see How to: Create a Test Project for SQL Server Database Unit Testing.
You have two options for creating a SQL Server unit test:
Create a new SQL Server unit test inside a new test class.
All SQL Server unit tests within a given test class will use the same TestInitialize and TestCleanup scripts. Create a new test class if you want your unit test to use different TestInitialize and TestCleanup scripts than other unit tests. For more information, see Scripts in SQL Server Unit Tests.
Create a new SQL Server unit test inside an existing test class.
Choose this option if your unit test will use the same TestInitialize and TestCleanup scripts as other unit tests within the class.
To create a SQL Server unit test inside a new test class
On the Test menu, click New Test.
The Add New Test dialog box appears.
Under Templates, click SQL Server Unit Test.
Under Test Name, enter a name for the test.
Under Add to Test Project, select an existing test project, into which to add this test. If no test project exists or if you want to create a new test project, select Create a new <language> test project.
If your test project is new, the New Test Project dialog box appears. Name the project and click OK.
If your test project is new or has not been configured, the SQL Server Test Configuration <ProjectName> dialog box appears. This dialog box allows you to configure the following information for your test project:
The database connection used to execute tests.
The database connection used to validate test results, deploy a database, and generate data.
The automatic deployment of the database project and any associated schema changes to a given project configuration before you run unit tests.
For more information, see How to: Configure SQL Server Unit Test Execution.
Provide project configuration information and click OK.
- or -
Click Cancel to create the unit test without configuring the test project.
Your blank test appears in the SQL Server Unit TestDesigner. Depending on the language you specified for creating the test project, a Visual Basic or Visual C# source code file is added to the test project. This file contains the SQL Server unit test class that SQL Server Data Tools generates for the unit test you just created. This test class can contain one or more unit tests that you can add through the SQL Server Unit Test Designer or through code as new test methods in the test class.
You can also add additional tests by:.
Right clicking on a test project in Solution Explorer, selecting Add, New Test, and then SQL Server Unit Test.
In SQL Server Object Explorer, select Create Unit Tests.
When you select this file in Solution Explorer, it is displayed in the SQL Server Unit Test Designer, by default. To view the code or to customize it to add more functionality to your unit tests, select the file, right-click, and choose View Code.
To create a SQL Server unit test inside an existing test class
Open an existing SQL Server unit test class in the SQL Server Unit Test Designer. You can access the SQL Server Unit Test Designer by double clicking the unit test source code file in Solution Explorer.
Click the plus (+) sign in the navigation bar to display the Specify a unit test name dialog box.
Type a name and click OK.
Your new SQL Server unit test is available in the drop-down list in the navigation bar. It is also added as a new test method in the test class. To view the test method in code, select the class file, right-click, and choose View Code. The name of the current test class file is displayed on the tab at the top of the SQL Server Unit Test Designer.
After you have configured the test project and created the unit test, the next steps are:
Add a Transact-SQL test script.
Define pre-test and post-test actions.
Add test conditions or other assert statement to verify the script results.
The Inconclusive test condition is the default condition added to every test. This test condition is included to indicate that test verification has not been implemented. Delete this test condition from your test after you have added other test conditions. For more information, see How to: Add Test Conditions to Database Unit Tests.