Troubleshooting SQL Server Database Unit Testing Issues

You might encounter the following issues when you work with SQL Server unit tests on a

database.

If you modify the

file in the test project, you must rebuild the test project before

the changes take effect. These changes include any changes you make to

with the

Test Configuration

dialog box. If you don’t rebuild the test project, the changes

aren’t applied when you run the unit tests.

If you deploy a database from a database project when you run unit tests, the database is

deployed by using the connection string information specified in your unit test configuration.

The connection information that is specified in the database project Debug properties isn’t

used for this task, which allows you to run SQL Server unit tests against different instances of

the same database.

If your database unit tests are failing because of a timeout, you can increase the timeout period

by updating the

file in your test project. The connect timeout, defined on the

connection string, specifies how long to wait when the unit test connects to the server. The

command timeout, which must be defined directly in the

file specifies how long to

wait when the unit test executes the Transact-SQL script. If you have problems with long

running unit tests, try increasing the command timeout value in the appropriate context

element. For example, to specify a command timeout of 120 seconds for the

element, update the

as follows:

XML

app.config app.config app.config app.config app.config