SQL Server 2005 - Designing a Unit Test Plan for a Database
<p> A database is really a complex group of objects – objects that retrieve data, objects that perform actions, objects that guard data, and so on – that work together to manage your data. As complex as they are, databases evolve. Applications connecting to the database will require additions and new features to address new business requirements. However, when you are making the changes, how can you be sure that you are not breaking compatibility with other client applications? How can you ensure that, by fixing some logic written in a stored procedure, you are not breaking the overall process that this single stored procedure was just a part of?</p> <p> The answer is testing. Testing provides the solution for evaluating how the database will behave after a modification has been made on the database. You can execute different types of testing on a piece of software, such as a database, depending on what you want to evaluate or find out about its execution, such as whether it behaves as expected, performs as expected, is a secure as expected, scales as expected, and so on.</p> <p> In this session, you will learn the key design practices for designing a unit testing plan for a database so that you can quickly pinpoint where to focus your attention when problems arise. A unit test plan is the building block for creating a performance baseline and a benchmark strategy.</p> <p> </p> <p> Session objectives 10 min each:</p> <p> Design a unit test plan for a database.</p> <ul> <li> Asses which components should be unit tested.</li> <li> Design a test for query performance.</li> <li> Design a test for data consistency.</li> <li> Design a test for application security.</li> <li> Design a test for system resources utilization.</li> <li> Design a test to ensure code coverage.</li> </ul>
Rick Martinez
SQL Server
Mobile Home
Sessions
Schedule
Presenters
Rooms
Login