Highlights

Code coverage scope defined with regular expressions

utplsql run has four new options that decide what is included in the coverage report by schema or object name pattern:

When project files are mapped to database objects (-source_path / -test_path), coverage is already limited to those files.
The new options are for code that cannot be mapped to project files. They allow for new packages that follow your naming conventions
to be covered (or left out) automatically, without updating a list of schemas or objects in your pipeline.

utplsql run app/pass@db -p=app -f=ut_coverage_html_reporter -o=coverage.html \
  -include-schema-expr='^APP_' -exclude-schema-expr='_TEST$' -exclude-object-expr='_TMP$'

• Expressions are case-insensitive Oracle regular expressions. Object expressions are matched against the object name without the schema.
• If an include expression is given, --coverage-schemes and -include are ignored. All exclude options are always applied.
• The filters do not apply when coverage is gathered on project files (-source_path / -test_path).

See Filtering objects in coverage reports
and the utPLSQL-cli documentation.

The utPLSQL Maven plugin supports the same filters (includeSchemaExpr, excludeSchemaExpr, includeObjectExpr, excludeObjectExpr)
and now documents them in detail.

What's Changed

• Add coverage filter options by regular expression by @jgebal in #233
• Announce releases with the shared announce-release action by @jgebal in #234

Full Changelog: v3.2.1...v3.2.2

Contributors

What's Changed

• Allow /@TNS connections using Oracle Wallet (Secure External Password Store) by @jgebal in #230
• Update of java-api-version dependency by @jgebal in #231
• Don't reveal credentials in log and error output by @jgebal in #232

Full Changelog: v3.2.0...v3.2.1

Contributors

What's Changed

• Bump ch.qos.logback:logback-classic from 1.2.11 to 1.2.13 by @dependabot[bot] in #223
• update libraries dependencies by @jgebal in #228
• Update to Java 17 by @jgebal in #229
• Update to utPLSQ-java-api 3.2.4 (using ojdbc version 23.7.0.25.01)

Full Changelog: 3.1.9...v3.2.0

Contributors

What's Changed

• Bugfix/Locale-Info and Nullpointer by @pesse in #171
• Feature/cleanup maven jdbc by @jgebal in #176
• Support a_coverage_schemes option of utPLSQL by @pesse in #180
• Feature/GitHub actions by @jgebal in #202
• Add new --ora-stuck-timeout parameter by @pesse in #198
• Update dependencies by @pesse in #204

Full Changelog: v3.1.8...3.1.9

Contributors

Compatibility

This version of utPLQL-cli is compatible with all versions of utPLSQL from 3.0.0 to 3.1.8. We encourage you to always use the latest version of cli to communicate with a v3 core.

Changes in this release

New Features

• Due to the recent Oracle license changes, utPLSQL-cli is now shipped with all necessary ojdbc drivers!

Enhancements

• Default-parameters of the utPLSQL core API are now correctly used when not specified

Bugfixes

• Coverage reports are now correctly created (#162, #165)
• File-mapping also works now for utPLSQL core 3.0.0-3.0.2 (utPLSQL/utPLSQL-java-api#92)

Internal enhancements

• Use publicly available ojdbc libraries
• Better coverage self-tests

Compatibility

This version of utPLQL-cli is compatible with all versions of utPLSQL from 3.0.0 to 3.1.7. We encourage you to always use the latest version of cli to communicate with a v3 core.

Changes in this release

New Features

• CLI is now runnable from Java 8-12 (and probably also upcoming versions)
• CLI now uses Picocli instead of JCommander. This might have some impact on how parameters are interpreted, for example on windows machines when you define -f=ut_documentation_reporter -o="output.txt" you will have to enclose the "output.txt" part as shown
• Support for Tags via --tags=tag1[,tag2[,tag3]]parameter (#157)
• Support for random order of test execution via -r/--random-test-order and -seed/--random-test-order-seed (#139)
• Ability to enable DBMS_OUTPUT from cli via -D/--dbms_output (#137)

Enhancements

• Completely removed HikariCP (#158)
• A warning is shown if orai18n.jar is not on the classpath. This is highly recommended due to some strange behaviour of the jdbc-driver otherwise (#146, #153)

Bugfixes

• Type mapping (-type_mapping) parameter is now interpreted correctly (#143)

Internal enhancements

• Improvement of tests
• Refactoring towards immutability
• Added some more debug information

Compatibility

This version of utPLQL-cli is compatible with all versions of utPLSQL from 3.0.0 to 3.1.6. We encourage you to always use the latest version of cli to communicate with a v3 core.

Changes in this release

New Features

• CLI now logs some basic information to screen in addition to an eventually configured to-screen-reporter (#89, #76)
  • This output can be avoided with the new -q, --quiet parameter
  • Much more logging can be output with the new -d, --debug parameter
• It's possible to connect as sysdba now via utplsql run "sys as sysdba"/pw@connectstring (#115)
• The default timeout of 60 minutes is now configurable via the new -t, --timeout parameter (#124)

Enhancements

• Timeout now returns error exit-code (#129)
• In case of Oracle stuck-scenario during createStatement, a warning is written to the screen and the same call for running the tests is retried up to 5 times. (#20)
• It's now possible to pass usernames containing / and passwords containing @ by encapsulating those in the connectstring with ": utplsql run "my/User"/"P@ssword"@server:1521/Service (#111)
• API-version is now stored in a separate, non-compiled file

Bugfixes

• Info command should now show the correct version information (#108)
• Non-argument call will output help (#110)

Internal enhancements

• Update of HikariCP
• Improvement of passing user/pw/connect info to connection pool
• Improvement of Error-Handling
• Cleanup of tests

Compatibility

This version of utPLQL-cli is compatible with all versions of utPLSQL from 3.0.0 to 3.1.3. We encourage you to always use the latest version of cli to communicate with a v3 core.

Changes in this release

New Features

• New command utplsql info [user/password@connectstring] #77
• New command utplsql reporters user/password@connecstring
• Cli tries to connect to oracle via thick-driver first and use thin-driver as fallback #88 #90 #91

Enhancements

• Limit number of connections to number of reporters+1 #85
• Include JAXB library so utPLSQL-cli can be run on java 9+10 #82
  • There is however still a problem when using HTMLCoverageReporter and Java 9/10
• Improved documentation and help-command #31
• An existant NLS_LANG-variable will now lead to corresponding ALTER SESSION statements when connecting #101

Bugfixes

• HTML Coverage assets are placed and referenced correctly when using output file in subdirectory #94
• Java-locale is now correctly derived from LC_ALL or LANG environment variable, not from NLS_LANG #101

Internal enhancements

• Refactoring of Command architecture
• Refactoring of Connection handling
• Improved Error handling

Compatibility

This version of java-api is compatible with all versions of utPLSQL from 3.0.0 to 3.1.0. We encourage you to always use the latest version of cli to communicate with a v3 core.

Changes in this release

Enhancements

• Support for custom reporters. Just call utplsql run user/pass@connstr -f=my_custom_reporter and cli will try to use a database-reporter with the given name
• Assets necessary for CoverageHTMLReporter are written to $outputFileName-assets folder (utPLSQL/utPLSQL-java-api#39)
• Realtime-Feedback: Output to screen is immediate, output to files is in bulks (#68)
• NLS-Support from environment (#56)

Bugfixes

• The correct usage is now stated in help message (#63)
• Several small improvements

First official release of utPLSQL-cli - Command line client for utPLSQL v3

Requirements

• Java8
• Oracle JDBC driver file (ojdbc8.jar) is required
• Oracle i18n driver file (orai18n.jar) is required for national character-set support

Both driver files need to be downloaded and placed in utPLSQL-cli/lib folder

Key features

• connectivity to Oracle database without Oracle client software (needs JDBC driver)
• support for multiple reporters and multiple output files
• real-time reporting to screen (depends on reporter implementation)
• documentation reporting in color
• mapping of project files to database objects (needed for Sonar reporting)
• support for customized project file-mapping rules

utPLSQL versions supported

• utPLSQL v3.0.0
• utPLSQL v3.0.1
• utPLSQL v3.0.2
• utPLSQL v3.0.3
• utPLSQL v3.0.4