This course is aimed at technical leads, development or project managers who are looking after database development projects. It discusses both why database unit testing is a best practice, and how to get the business buy-in necessary to adopt it. This is a less technical course, which helps show why gaining business buy-in to new processes such as database unit testing is important, and can be a key enabler for adoption of best practices.
Introduction Welcome to this course on making the case for database unit testing. My name is Dave Green, and I'm recording this course for Pluralsight. This module will introduce you to the terms and concepts of unit testing, and look at the overall business benefit which we are trying to drive. In later modules, we will be examining why we want to unit test from a business perspective, to give you the tools necessary to convince the business to try unit testing for databases, and how to evaluate the usefulness of it when they have tried it. We will then look at implementation considerations. What you need to know when implementing database unit testing, how it differs from application testing, and why, and where it is the same. We'll look at how you might start unit testing, whether you have an existing code base or are starting on a new project without exiting code to manage. Regardless of the point you start from, we will also look at how to evaluate the results, the information that you need to have collected to justify your investment, and how to present this to various parts of a business to ensure you can continue to get the benefits of unit testing. We will finish off with a look at how you can build on unit testing with your databases to get more certainty around database development, and to continue to reduce risk.
Business Focus Hello. This course is on making the case for database unit testing. This module is on the business focus. My name is Dave Green and I am recording this course for Pluralsight. In this course we're going to look at the definition of unit testing. We're going to look at what it is that we're trying to achieve with unit testing, why we do it, and we're going to look at how that can drive business value. We're going to look at some of the costs that are associated with database unit testing and starting a database to database unit test. We're also going to look at how you can estimate how long unit testing will take, what it does to your business processes, and how you can allow for those in advance and then we will look at how these processes themselves may need to change.
Implementation Considerations Hello and welcome to this module on implementation considerations, part of the course making the case for database unit testing. My name is Dave Green and I'm recording this course for Pluralsight. In this module we will be looking at how to choose a framework, how to develop with it, both in terms of new developments and maintenance to existing code, but we're looking at how to get started, and also some decisions that, if we make correctly now, will really help us in the longer term.
Conclusions and Next Steps Welcome to this module on Conclusions and Next Steps. Part of the course making the case for database unit testing. My name is Dave Green and I am recording this course for Pluralsight. In this course we have looked at why you would want to unit test, how to sell the idea to the business, and how to start unit testing your databases. Let's look at some of the conclusions we can draw. Firstly, it's important to note that it is possible to do unit testing for the database. This is a lot younger as a process than unit testing within applications, so this may need to be demonstrated rather than being accepted as a given, and in any case, implementing the best practice of unit testing comes at a cost, which needs to be justified. We will find that both in order to get initial approval and justify continuing to unit test our databases we need to engage with the rest of the business and demonstrate how it helps. This helps make our implementation more successful, not least as our colleagues will understand the change. We shouldn't just launch into the process, just as we wouldn't launch into coding without understanding what it is that we are aiming to achieve. That aim can be refined over time, but should still exist. Unit testing can help to bring more planning and control to our day to day database development by moving more of that planning up front. It's important to note that the introduction of unit testing to the business and the adoption of it represents the first few steps on a journey, not the endpoint. There are other areas and best practices, which we can adopt to build on the hard work of implementing database unit testing.