Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
By configuring your test project, you can specify several settings that control aspects of how your SQL Server unit tests are run. These configuration settings are stored in your test project's app.config file. If you edit this file directly, the new values appear in the test configuration dialog box.
Your solution can contain multiple test projects. Each test project contains one app.config file (that is, one set of configuration settings). As a result, your solution can contain different sets of unit tests (one set for each test project) that are configured to run differently.
These settings control how your test connects to the database that you test, how you deploy a schema from a database project to that database:
Database Connections. You use this setting to specify the connection strings that are used to connect to the database that you're testing. For more information, see Specify Connection Strings
Schema deployment. A database project is an offline representation of your database. The database project represents the structure of your database objects but contains no data. After you make schema changes in a database project, you can test them in an actual database. In the schema deployment step, database objects that you want to test are copied from your database project into the database on which you run tests. For more information about schema deployment, see Deploy a Database Schema.
Note
Tests don't run in the solution folder but in a separate folder on the local hard disk. Although you can configure aspects of test deployment, you typically don't need to configure them for unit tests. For more information about test deployment, see Running Tests.
Specify connection strings
Specify database connection strings
Right-click on the unit test project in Solution Explorer and select SQL Server Test Configuration.
The SQL Server Test Configuration -'<projectname>' dialog box appears.
Under Database Connections, you can do the following steps:
Select the database connection against which you want to execute unit tests.
Select the Use a secondary data connection to validate unit tests check box, and select a database connection in the list if you want test execution to be validated against a different database connection.
Select New Connection to add a connection to either list. You can also select Edit Connection to modify settings on an existing connection.
This step creates the
ExecutionContextconnection string, which is used to execute the test script in your unit test. If you also specify a secondary connection, thePrivilegedContextconnection string is also created. This connection is used to test interactions with the database outside the test script in your unit test. For more information, see Overview of connection strings and permissions.Select OK to close the SQL Server Test Configuration -'<projectname>' dialog box.
Rebuild the test project to apply the configuration changes.
Deploy a database schema
Deploy to a database the schema of a database project
In Solution Explorer, right-click your database project, and then select Build.
When you build your database project, you generate a Transact-SQL script. This script, when it runs against a database, recreates the structure of your database project in that database.
Select the test project that you want to configure.
Right-click on the unit test project in Solution Explorer and select SQL Server Test Configuration.
The SQL Server Test Configuration -'<projectname>' dialog box appears.
Under Deployment, you can do the following steps:
Select the Automatically deploy database projects before running tests check box to make sure that any schema changes that you have made to your database project are committed before tests are run.
Under Database Project, select the database project that you want to deploy, or select the ellipsis to browse for another project. Database project files have the extension
.dbproj.Under Deployment Configuration, select the project configuration against which you want to deploy. Your choices are Debug, Default, or Release. However, if you create a configuration for unit testing, that configuration also appears as an option.
Select OK to close the SQL Server Test Configuration -'<projectname>' dialog box.
At the start of the test run, the Transact-SQL script that was generated in step 1 is run. This action deploys the schema to the target database.
Rebuild the unit test project to apply the configuration changes.