← 返回首页
utPLSQL-java-api/README.md at develop · utPLSQL/utPLSQL-java-api · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted
Cancel Submit feedback

Saved searches

Use saved searches to filter your results more quickly

Cancel Create saved search
Appearance settings
Resetting focus

Files

 develop

Breadcrumbs

  1. utPLSQL-java-api

README.md

Blame
Blame

Latest commit

 

History

History
112 lines (84 loc) · 4.51 KB
 develop

Breadcrumbs

  1. utPLSQL-java-api

README.md

Top

File metadata and controls

  • Preview
  • Code
  • Blame
112 lines (84 loc) · 4.51 KB

utPLSQL-java-api

This is a collection of classes, that makes it easy to access the utPLSQL v3 database objects using Java.

  • Uses ut_runner.run methods to execute tests.
  • Can gather results asynchronously from multiple reporters.
  • Handles compatibility for all 3.x versions of utPLSQL

Downloading

This is a Maven Library project, you can add on your Java project as a dependency.

Notice: You no longer need to configure an additional repository. The library is available in Maven Central since version 3.1.15.

<dependency> <groupId>org.utplsql</groupId> <artifactId>utplsql-java-api</artifactId> <version>3.2.3</version> </dependency>

Compatibility

The latest Java-API is always compatible with database frameworks of the same minor version. For example API-3.2.3 is compatible with database framework 3.2 but not with database framework 3.0 or 3.3

It is although recommended to always use the latest release of the API to build your tools for utPLSQL.

Usage

You can find examples for many features of the java-api in the Unit- and Integration tests.

Test-Runner

Executing tests using default parameters:

try (Connection conn = DriverManager.getConnection(url)) { new TestRunner().run(conn); } catch (SQLException e) { e.printStackTrace(); }

Executing tests and printing results to screen:

try (Connection conn = DriverManager.getConnection(url)) { Reporter documentationReporter = new DocumentationReporter().init(conn); new TestRunner() .addReporter(documentationReporter) .run(conn); documentationReporter .getOutputBuffer() .setFetchSize(1) .printAvailable(conn, System.out); } catch (SQLException e) { e.printStackTrace(); }

Optional Features

There might be some features which are not available in previous versions of utPLSQL. These "optional features" are listed in the enum org.utplsql.api.compatibility.OptionalFeatures and their availability can be checked against a connection or Version-object:

OptionalFeatures.CUSTOM_REPORTERS.isAvailableFor( databaseConnection );

Compatibility-Proxy

To handle downwards-compatibility, java-api provides an easy to use CompatiblityProxy, which is instantiated with a connection. It will check the database-version of utPLSQL and is used in several other features like TestRunner and ReporterFactory. You can also ask it for the database-version.

try (Connection conn = DriverManager.getConnection(url)) { CompatiblityProxy proxy = new CompatibilityProxy( conn ); Version version = proxy.getUtPlsqlVersion(); } catch (SQLException e) { e.printStackTrace(); }

Reporter-Factory

The java-api provides a ReporterFactory you can use to inject your own implementations of (java-side) reporters or reporter-handlers. It also provides a more generic approach to Reporter-handling.

If you request the Reporter-Factory for a Reporter it has no specific implementation for it will just return an instance of a DefaultReporter with the given name as SQL-Type, assuming that it exists in the database. Therefore, you can address custom reporters without the need of a specific java-side implementation.

try (Connection conn = DriverManager.getConnection(url)) { ReporterFactory reporterFactory = ReporterFactory.createDefault( new CompatibilityProxy( conn )); reporterFactory.registerReporterFactoryMethod(CoreReporters.UT_DOCUMENTATION_REPORTER.name(), MyCustomReporterImplementation::new, "Custom handler for UT_DOCUMENTATION_REPORTER"); Reporter reporter = reporterFactory.createReporter(CreateReporters.UT_DOCUMENTATION_REPORTER.name()); } catch (SQLException e) { e.printStackTrace(); }

Contributing

See CONTRIBUTING.md

Footer

© 2026 GitHub, Inc.