So I come up to the editor tool bar and set Execute PL/SQL. The process of creating unit test simply begins with executing the code in a normal way. Now I want to create a unit test for it and make sure I have a range of unit tests that cover multiple use cases, just to make sure that any future changes to this code won't introduce any bugs. So this is a stored procedure that has been recently modified. What we're seeing here is a piece of code that we covered in some of the early demos around profiling and SQL optimization. So let's get into a demo to show you how easy it is to create unit tests in. And unit testing also becomes an essential part of moving your traditional develop processes to agile through automation. Unit tests can be stored in a repository so they can be used in future regression testing. Simplifying the unit test creation workflow makes it more likely that more developers will create tests for their code. Testing also helps to document ongoing code development, given the amount of PL/SQL code that is legacy. Untested PL/SQL code can introduce bugs in production, which can lead to expensive rework and associated business cost.

So why is this important? Well, unit tests ensure that your PL/SQL code is functionally capable and covers all known use cases. In Step 5, I'm going to show you how easy it is to create a simple PL/SQL unit test using Toad. And welcome to this multi-part series on enabling agile database development using Toad for Oracle. My name is John Pocknell, Toad for Oracle Product Manager.

Toad pl sql