Annotations are used to configure tests and suites in a declarative way similar to modern OOP languages. This way, test configuration is stored along with the test logic inside the test package.

No additional configuration files or tables are needed for test cases. The annotation names are based on popular testing frameworks such as JUnit.

The following are best practices we at utPLSQL have learned about PL/SQL and Unit Testing.

utPLSQL comes with a built-in coverage reporting engine. The code coverage reporting uses package DBMS_PROFILER (and DBMS_PLSQL_CODE_COVERAGE on Oracle database version 12.2 and above) provided with Oracle database.

Code coverage is gathered for the following source types:

utPLSQL is responsible for handling exceptions wherever they occur in the test run. The framework is trapping most of the exceptions so that the test execution is not affected by individual tests or test packages throwing an exception.

The framework provides a full stacktrace for every exception that was thrown. The reported stacktrace does not include any utPLSQL library calls in it.

utPLSQL provides several reporting formats. The sections below describe most of them.

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

*

*/

subtype t_executable_type is varchar2(30);

gc_before_all constant t_executable_type := 'beforeall';