There are tools available from Microsoft, as well as from a number of third party vendors, to ease the process of integrating database unit testing into your development environments and your continuous delivery pipeline.

This session isn't about any of those tools, but is an attempt to get back to basics - with the open source tSQLt framework - and address questions such as:

• Why is database unit testing important?
• Why is database unit testing difficult?
• What do I need to test?
• What do I not need to test?
• What does a "good" unit test look like?

No particular experience of automated testing is required, we'll be talking about database testing "from the ground up". A good grasp of Transact-SQL constructs will be helpful in understanding the examples.