This is a collection of classes, that makes 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.
This is a Maven Library project, you can add on your Java project as a dependency. At the moment, it's not available in any public Maven repository, but you can clone it and install as a local dependency (follow the Contributing session).
<dependency>
<groupId>org.utplsql</groupId>
<artifactId>java-api</artifactId>
<version>1.0-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
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);
new OutputBuffer(documentationReporter)
.printAvailable(conn, System.out);
} catch (SQLException e) {
e.printStackTrace();
}
To develop it locally, you need to setup your maven environment.
That's the easy part, you just need to download the Maven binaries and extract it somewhere, then put the maven/bin folder on your PATH.
https://maven.apache.org/install.html
Don't forget to configure your JAVA_HOME environment variable.
The library uses OJDBC Driver to connect to the database, it's added as a maven dependency. To be able to download the Oracle dependencies, you need to configure your access to Oracle's Maven Repository:
http://docs.oracle.com/middleware/1213/core/MAVEN/config_maven_repo.htm#MAVEN9010
Sections 6.1 and 6.5 are the more important ones, and the only ones you need if you're using the latest Maven version.
After configuring your access to Oracle's Maven repository, you will be able to successfully build this API.
cd utPLSQL-java-api
mvn clean package install -DskipTests
The cmd above is ignoring unit tests because it needs a database connection with the latest utPLSQL v3 installed. Please take a look on .travis.yml and .travis folder to see how testing was configured.