Hi, folks. My name is Denis O'Sullivan, and I'm a systems consultant with Quest. Today, I want to show you how you can quickly and easily add regression testing of PL/SQL code into your daily development routine. So on screen, I have a procedure loaded into the editor of Toad for Oracle. The first thing I'm going to do is debug this procedure. This procedure has one input, and I'm going to select 0 for this particular test, and quickly run the debug.
Once complete, I pop over to the PL/SQL Results tab, and select Create Unit Test. First thing I need to do is select the test definition. I can create a new or attach to an existing one. A test definition is a group of test cases. Then I need to give the test a meaningful name. And select OK.
So now this test case has been created and stored in my centralized unit testing repository. So now going forward, any of my development colleagues or I can quickly and easily call these unit tests whenever we're working on this procedure. To do so, I select the Execute Code Tester tests button. And from here, I can select which test definitions or unit test I want to run.
The output screen displays the results at a test definition level. So if all the test cases or the test definition run successfully, the test definition is deemed have run successfully. If one or more tests fail, than the entire test definition is deemed half failed.
In my case, my test definition regression is deemed to have been successful, because all the test cases belonging to it ran successfully. So now I have the peace of mind of knowing that I haven't broken something that was previously working. So this is how you can easily add regression testing of PL/SQL code into your daily routine. Thanks for tuning in.