Everyone that has been involved in the Database Development can notice how huge the impact of a bug can be, especially when these kind of mistakes could be easily avoided through the Test Driven Development (TDD) approach and the real implementation of Unit Testing on SQL Server objects as stored procedures, functions and triggers.

When you start to google search about how to start implementing Unit Testing for SQL Server you always find tSQLt as the first result returned, however, the extremely low number of downloads tell us about the issue with this implementation. Some possible causes could be explained, such as the lack of a free UI tool for executing the tests, but I have been working with many full-stack developers and one of the most important complaints is related to the fact that AAA (Arrange-Act-Assert) is not native and they can’t feel a soft transition in their regular tasks for Unit Testing with Databases.

In this presentation I would like to focus about how to get a better performance and good results through the SQL Unit Test feature of Visual Studio, how to overcome the main problems and how you will be able to use a free framework  (https://github.com/SimpleSqlUnitTesting/SimpleSqlUnitTesting) and extend it for your own convenience, otherwise I will be showing a simple way of installing it on the local machine or how you could extend to a centralized integration server.