From the course: DevOps for the Database with VSTS and Azure
Unlock the full course today
Join today to access over 22,400 courses taught by industry experts or purchase this course individually.
Why test?
- [Instructor] If you've been watching along the course, we've really made a lot of progress. Version control, work tracking, we've been able to get builds. And then we got automated deployments. And we sprinkled a little CICD magic around it. One thing though that we left out was the ability to unit test. And once again, had to do with my view of the world that it's not really a unit test when we have to deploy a database and get it configured. So when you think about why testing in databases, first thing is, really? Do we really have to explain why to test? Well, I think we do. And it's pretty straightforward, right? Humans write software, and we screw up. And because we make mistakes, we want to constantly check our work. And automated testing frameworks help us do that. The whole idea is that we can find defects before they get out to our customers. And again, it's the whole idea of shifting left, from where the development is done, to the right where the customer ultimately gets…
Contents
-
-
-
-
-
-
-
-
Why test?59s
-
What makes testing databases different?1m 48s
-
Good test data2m 22s
-
Testing locally with SSDT1m 19s
-
Testing locally with SSDT demo8m 20s
-
Testing as part of release1m 45s
-
Get tokenization task demo3m 7s
-
Add tokenization task to release demo2m 58s
-
Add test task to release demo4m 2s
-
Test locally with TSQLT1m 5s
-
Test locally with Slacker45s
-
Takeaways53s
-
-
-