CheckOps home

Tools directory

U

CheckOps

utPLSQL

utPLSQL is an Apache-2.0 unit testing framework for Oracle PL/SQL and SQL, with annotations, rich expectations and reporters for SonarQube, Jenkins and TeamCity.

Visit website

Latest public signals

Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.

Visit Website

Introduction

utPLSQL is a unit testing framework for Oracle PL/SQL and SQL that follows practices of modern frameworks like JUnit and RSpec.

Test suites are defined by annotating package specifications, and expectations compare complex types such as objects, collections and cursors natively. Reporters integrate with SonarQube, Jenkins and TeamCity. Installation runs install_headless.sql, which creates the UT3 schema.

In the quality loop utPLSQL tests database logic in Oracle.

The source code is at utPLSQL/utPLSQL on GitHub under the Apache-2.0 licence, with about 623 stars; the most recent commit was on 9 November 2026.

Features

  1. Annotations: –%suite and –%test.
  2. Expectations: Rich matchers.
  3. Complex type comparison: Objects, collections and cursors.
  4. Reporters: SonarQube, Jenkins, TeamCity.
  5. Coverage: Code coverage reports.
  6. CLI: utPLSQL-cli runner.

Pros

  1. Oracle standard: Mature community tool.
  2. Free to use: Open source under the Apache-2.0 licence, so the core tool costs nothing to use.
  3. Actively maintained: The repository had commits as recent as 9 November 2026.

Cons

  1. Oracle only: Not portable.
  2. Install in DB: Needs schema privileges.
  3. PL/SQL skills: Tests in PL/SQL.
create or replace package test_tax as
  --%suite(Tax)
  --%test(Applies standard rate)
  procedure standard_rate;
end;
/
exec ut.run('test_tax');

Resources:

Pricing

utPLSQL is free and open source under the Apache-2.0 licence.

  1. Oracle teams with PL/SQL code.

Conclusion

utPLSQL is the de facto unit test framework for PL/SQL.

Wire its reporters into CI.

On CheckOps, utPLSQL is filed under the Unit testing and Integration testing stages. Related tools listed here include pgTAP, SQLFluff, Atlas, Squawk, Database Lab Engine and dbt tests. A short trial on a real project, with your own code, data and pipeline, is usually the fastest way to choose between them, because fit matters more than feature lists. Facts here come from the official site, documentation and repository, checked on 11 November 2026.

Alternatives

Other tools on CheckOps that cover similar ground. Open a page, or compare one with utPLSQL side by side.