Toad uses the Oracle-provided DBMS_OUTPUT package, which contains functions for debugging PL/SQL code. When enabled, it uses a buffer that your PL/SQL code writes into and then a separate process queries the buffer out and displays the contents.
When you are running debugging in the Editor and DBMS output is enabled, a DBMS Output tab automatically displays the results of DBMS_OUTPUT.PUT_LINE() statements in the Editor. You can also edit the DBMS Output content to make comments, delete specific lines of output, and so on. The standard copy, cut, and paste keys also work in the DBMS Output box.
To view DBMS Output in the Editor, you must enable DBMS Output before executing PL/SQL. The output displays after the procedure has completed execution, not while you are stepping through the code. In nested procedure calls, all procedures must have run to completion before any DBMS Output content is displayed.
Note: Output only displays after the procedure has completed execution, not while you are single stepping through the code. In the case of nested procedure calls, all procedures must have run to completion before any DBMS Output content is displayed.
To enable or disable DBMS output
At the top of the DBMS Output window, click the Enable/Disable toggle button.
To generate DBMS Output
To automatically insert DBMS_OUTPUT statements
You can use Toad's Auto Debugger feature to automatically insert DBMS_OUTPUT statements where applicable and remove them when done.
If you do not see DBMS Output, try the following suggestions:
DBMS_OUTPUT results only display after the procedure has completed execution, not while you are single stepping through the code. In nested procedure calls, all procedures must have run to completion before any DBMS Output content is displayed.
To open the DBMS Output window
On the main toolbar, select View | DBMS Output.
You can edit the output display in the DBMS Output window. This allows you to note what you did to receive the output.
For example, when debugging a procedure named MyProc that expects a single number parameter, you can execute the procedure from an Editor window with the following statement:
begin MYPROC(1); end;
Prior to executing the above, you can document the call in the DBMS Output with a comment:
Calling MyProc with 1
Then turn DBMS Output ON and execute MyProc. The DBMS_OUTPUT statements will display after your notes about the call.
After you run PL/SQL with debugging, you can create a unit test for the active object in the PL/SQL Results window of the Editor. The test is created in the Code Tester for Oracle repository, which must exist in the connected database.
You can also run tests in this window. Toad supports a subset of the Code Tester functionality for creating a new test, but Toad provides a direct link to Code Tester if you need more advanced functionality.
To create and run tests, the following are required:
Note: Code Tester does not have to be running to create or run tests in Toad.
To create a unit test in Code Tester
In the Create Test Case dialog, complete the test information. You can change values as needed.
Note: By default, you are prompted to create a new test definition when you create the test case.
If you cannot create a test, the Code Tester repository on the database is not a supported version or does not exist. Select Attach to Existing to attach the test case to an existing definition.
To run a test from Toad
Click (Execute Code Tester for Oracle tests...).
To open Code Tester
Click on the PL/SQL Results toolbar or on the Code Tester Results dialog (after you run the test).
To add unit tests to Team Coding
You can include your unit tests in your Team Coding projects. This enables you to manage the revision history of your tests in the same way that you manage the revisions of your other controlled objects. The user/schema who created the tests in Toad must be included in (or added to) the Team Coding project for the tests to be controlled. For more information, see Configure Team Projects.