Skip to content


Running tests

utPLSQL framework provides two main entry points to run unit tests from within the database:

  • procedures and functions
  • procedures

These two entry points differ in purpose and behavior. Most of the time you will want to use as is designed for API integration and does not display the results to the screen.

Running from CI servers and command line

The best way to run your tests from CI server or command line is to use the utPLSQL-cli command line client.

Amongst many benefits it provides ability to: * see the progress of test execution for long-running tests - real-time reporting * use many reporting formats simultaneously and save reports to files (publish) * map your project source files and test files into database objects

You may download the latest release of the command line client from here or do it automatically using the command below (Unix).

# Get the url to latest release "zip" file
DOWNLOAD_URL=$(curl --silent | awk '/zipball_url/ { print $2 }' | sed -r 's/"|,//g')
# Download the latest release "zip" file
curl -Lk "${DOWNLOAD_URL}" -o
# Extract downloaded "zip" file
unzip -q

The ut package contains overloaded run procedures and functions. The run API is designed to be called directly by a developer when using an IDE/SQL console to execute unit tests. The main benefit of using this API is it's simplicity. A single line call is enough to execute a set of tests from one or more schemes.

The procedures execute the specified tests and produce output to DBMS_OUTPUT using the specified reporter. The functions can only be used in SELECT statements. They execute the specified tests and produce outputs as a pipelined data stream to be consumed by a select statement. procedures

The examples below illustrate different ways and options to invoke procedures.

alter session set current_schema=hr;
set serveroutput on
Executes all tests in current schema (HR).

set serveroutput on
Executes all tests in specified schema (HR).

set serveroutput on

Executes all tests from all packages that are on the com.my_org.my_project suitepath. Check the annotations documentation to find out about suitepaths and how they can be used to organize test packages for your project.

set serveroutput on
Executes all tests from package hr.test_apply_bonus.

set serveroutput on
Executes single test procedure hr.test_apply_bonus.bonus_cannot_be_negative.

set serveroutput on
Executes all tests from package hr.test_apply_bonus and all tests from schema cust.

set serveroutput on

Executes all tests from package hr.test_apply_bonus and all tests from schema cust.

set serveroutput on

Executes all tests from package hr.test_apply_bonus and all tests from schema cust.

Using a list of items to execute allows you to execute a fine-grained set of tests.

List can be passed as a comma separated list or a list of ut_varchar2_list objects or as a list within ut_varchar2_list.


ut_documentation_reporter is the default reporter for all APIs defined for running unit tests.

The procedures and functions accept a_reporter attribute that defines the reporter to be used in the run. You can execute any set of tests with any of the predefined reporters.

set serveroutput on
begin'hr.test_apply_bonus', ut_junit_reporter());
Executes all tests from package HR.TEST_APPLY_BONUS and provide outputs to DBMS_OUTPUT using the JUnit reporter.

For details on build-in reporters look at reporters documentation. functions

The functions provide exactly the same functionality as the procedures. You may use the same sets of parameters with both functions and procedures. The only difference is the output of the results. Functions provide output as a pipelined stream and therefore need to be executed as select statements.


When running tests with functions, whole test run is executed as autonomous transaction. At the end of the run, the transaction is automatically rolled-back and all uncommitted changes are reverted.


select * from table('hr.test_apply_bonus', ut_junit_reporter())); procedures

The ut_runner package provides an API for integrating utPLSQL with other products. Maven, Jenkins, SQL Develper, PL/SQL Developer, TOAD and others can leverage this API to call utPLSQL.

The main difference compared to the API is that does not print output to the screen. accepts multiple reporters. Each reporter pipes to a separate output (uniquely identified by output_id). Outputs of multiple reporters can be consumed in parallel. This allows for live reporting of test execution progress with threads and several database sessions. API is used by utPLSQL-cli, utPLSQL-SQLDeveloper extension and utPLSQL-maven-plugin and allows for: - deciding on the scope of test run (by schema names, object names, suite paths or tags ) - running tests with several concurrent reporters - real-time reporting of test execution progress - controlling colored text output to the screen - controlling scope of code coverage reports - mapping of database source code to project files - controlling behavior on test-failures - controlling client character set for HTML and XML reports - controlling rollback behavior of test-run - controlling random order of test execution

Running with multiple reporters.

  • in the main thread (session), define the reporters to be used. Each reporter has it's output_id and so you need to extract and store those output_ids.
  • as a separate thread, start and pass reporters with previously defined output_ids.
  • for each reporter start a separate thread and read outputs from the reporter.get_lines table function or from reporter.get_lines_cursor() by providing the reporter_id defined in the main thread.
  • each reporter for each test-run must have a unique reporter_id. The reporter_id is used between two sessions to identify the data stream


--main test run ( session 1 )
  l_reporter      ut_realtime_reporter := ut_realtime_reporter();
  l_reporter.set_reporter_id( 'd8a79e85915640a6a4e1698fdf90ba74' );
  l_reporter.output_buffer.init(); (ut_varchar2_list ('ut3_tester','ut3$user#'), ut_reporters( l_reporter ) );

--report consumer ( session 2 )
set arraysize 1
set pagesize 0

select * 
  from table(
--alternative version of report consumer ( session 2 )
set arraysize 1
set pagesize 0

  from dual;

Order of test execution

Default order

When unit tests are executed without random order, they are ordered by: - schema name - suite path or test package name if --%suitepath was not specified for that package
- --%test line number in package

Random order

You can force a test run to execute tests in random order by providing one of options to - a_random_test_order - true/false for procedures and 1/0 for functions - a_random_test_order_seed - positive number in range of 1 .. 1 000 000 000

When tests are executed with random order, randomization is applied to single level of suitepath hierarchy tree. This is needed to maintain visibility and accessibility of common setup/cleanup beforeall/afterall in tests.


set serveroutput on
begin'hr.test_apply_bonus', a_random_test_order => true);

select * from table('hr.test_apply_bonus', a_random_test_order => 1));

When running with random order, the default report (ut_documentation_reporter) will include information about the random test run seed. Example output:

Finished in .12982 seconds
35 tests, 0 failed, 0 errored, 1 disabled, 0 warning(s)
Tests were executed with random order seed '302980531'.

If you want to re-run tests using previously generated seed, you may do so by running them with parameter a_random_test_order_seed Example:

set serveroutput on
begin'hr.test_apply_bonus', a_random_test_order_seed => 302980531);

select * from table('hr.test_apply_bonus', a_random_test_order_seed => 302980531));


Random order seed must be a positive number within range of 1 .. 1 000 000 000.

Run by Tags

In addition to the path, you can filter the tests to be run by specifying tags. Tags are defined in the test / context / suite with the --%tags-annotation (Read more).
Multiple tags are separated by comma. The framework applies OR logic to all specified tags so any test / suite that matches at least one tag will be included in the test run.

begin'hr.test_apply_bonus', a_tags => 'test1,test2');
select * from table('hr.test_apply_bonus', a_tags => 'suite1'))

You can also exclude specific tags by adding a - (dash) in front of the tag

select * from table('hr.test_apply_bonus', a_tags => '-suite1'))

Keeping uncommitted data after test-run

utPLSQL by default runs tests in autonomous transaction and performs automatic rollback to assure that tests do not impact one-another and do not have impact on the current session in your IDE.

If you would like to keep your uncommitted data persisted after running tests, you can do so by using a_force_manual_rollback flag. Setting this flag to true has following side-effects:

  • test execution is done in current transaction - if while running tests commit or rollback is issued your current session data will get commited too.
  • automatic rollback is forced to be disabled in test-run even if it was explicitly enabled by using annotation `--%rollback(manual)

Example invocation:

set serveroutput on
begin'hr.test_apply_bonus', a_force_manual_rollback => true);


This option is not available when running tests using as a table function.

Reports character-set encoding

To get properly encoded reports, when running utPLSQL with HTML/XML reports on data containing national characters you need to provide your client character set when calling functions and procedures.

If you run your tests using utPLSQL-cli, this is done automatically and no action needs to be taken.

To make sure that the reports will display your national characters properly when running from IDE like SQLDeveloper/TOAD/SQLPlus or sqlcl you need to provide the charaterset manualy to

Example call with characterset provided:

begin'hr.test_apply_bonus', ut_junit_reporter(), a_client_character_set => 'Windows-1251');

Last update: February 23, 2022 22:55:42
Created: February 26, 2017 02:13:22