Skip to content

Announcements

Auto-run utPLSQL tests with Oracle sqlcl

Today at #apexConn19.

Sam Nitsche (blogger, presenter, testing & compassionate-coding advocate, utPLSQL-cli & utPLSQL-api developer) met with Kris Rice (Oracle SQLDeveloper, sqlcl, ORDS rock-star, developer, advocate, presenter, mentor)

As a result, something amazing happened. Within an hour or so, Kris created a fully functional auto-runner for utPLSQL tests within Oracle sqlcl.

utPSLQL-sqlcl

See for yourself

If you want to use sqlcl to run your tests, each time you compile a package, have a look at this script for sqlcl.

Huge thank you to Kris and Sam!

Amazing things can happen when right people meet at right time in right place.

  • in news
  • 1 min read

Oracle 19c DB added to our CI/CD process

We take all the possible effort to assure utPLSQL can be tested against t all supported Oracle database versions.

Today, our automation got enriched with Oracle 19c database testing.

Pavel Kaplya has prepared a new small Docker Image for Oracle 19c.

Note:

You can take advantage of our efforts and build your own small Docker images (non-PDB) using our docker-scripts.

Continuous testing of utPLSQL

utPLSQL is now getting tested against five database versions: - Oracle 11g XE - Oracle 12c R1 - Oracle 12c R2 - Oracle 18c - Oracle 19c

You can see our build process & test results on travis-ci.org/utPLSQL

All of our deliverable projects use set of tools that are free to sue for Open-Source: - static code analysis using sonarcloud - publishing code coverage using coveralls - deploying java-api artifacts to packagecloud - deploying utPLSQL-cli artifacts to bintray - maven plugin publishing into maven repository

All of our builds must pass quality gates (code quality/tests/code coverage) before we approve and merge pull requests.

Changes in release 3.1.6

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.

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

Bugfix release for v3.1.5

Bug fixes

  • Fixed a bug in release 3.1.5 where to_equal matcher was failing due to privileges when comparing non sql diffable types #870

Improvements

  • Reduced number of information displaying about user defined type. We will now display only type name instead of full structure #866

Changes in release 3.1.4

New features

  • Added to_contain matcher for collections and cursors #79
  • Added unordered_columns (uc) option for cursor comparison to ignore the order of the columns #779
  • Added ut_debug_reporter for debug logging #480
  • Added ut_realtime_reporter for utPLSQL-SQLDeveloper extension #795

Enhancements

  • Improved performance of cursor comparison #780
  • Added support for installation on databases with block size < 8KB #848
  • Added initial timeout to ut_output_buffer #840
  • Enhanced performance of get_reporters_list function #814
  • Moved calls of dbms_lock.sleep to dbms_session for newer DB versions #806
  • utPLSQL coverage will now work without re-install after DB-upgrade from 12.1 to 12.2 #803

Bug fixes

  • Fixed problem with REGEXP in annotation parsing with NLS CANADIAN FRENCH #844
  • Fixed issue with Rollback to savepoint failing on distributed transaction #839
  • Fixed reporting of differences when comparing collections scalar values #835
  • Fixed issue with test run failing due to too many transaction invalidators #834
  • Fixed randomly occurring error during cursor comparison #827
  • utPLSQL install script will now support special characters in passwords #804

Documentation improvements

  • Fixed documentation examples for context annotation #851
  • Added description on how to check version of utPLSQL #822

Internal enhancements

  • Implemented Sonar analysis on DBA Views #850
  • Finished migration from old-tests #475
  • Fixed shell scripts to support multiple unix dialects (especially for macOS) #796
  • Added info on project support from Redgate #841
  • Added code_of_conduct #836
  • Added issue tempates #842
  • Added utPLSQL logo #845

Changes in release 3.1.3

New features

  • added function ut_runner.is_test #788
  • added function ut_runner.is_suite #787
  • added function ut_runner.has_suites #786
  • added ability to disable automatic rollback for a test-run #784
  • when invoked with package name, utPLSQL will now run only tests from specified package even if package has child packages by suitepath #776

Enhancements

  • Improved performance of schema-scanning and utPLSQL startup #778
  • Improved performance of output-buffer #777
  • Improved documentation to mention ability to pass client encoding for HTML & XML reports #775
  • Improved documentation for cursor comparison to mention challenges with TIMESTAMP bind variables

Bug-fixes

  • utPLSQL code coverage will now work properly with long object names #716
  • utPLSQL installation will now also work properly, when user performing the install has ANY grants #737
  • fixed documentation bug for --%context with --%displayname #726
  • fixed Teamcity reporter issues with missing escape for some characters and long messages #747
  • fixed issue with sonar test results reporter when contexts are used #749
  • fixed issue with ORA-07455 getting thrown on cursor comparison #752
  • fixed issue with wrong failure message for unordered data #764
  • fixed missing privilege issue for unordered/join-by cursor data comparison #765 #770

Internal enhancements

  • added suite-level cache to allow for faster retrieval of suite contents and enable implementation of additional features #783

Changes in release 3.1.2

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.

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

Changes in release 3.1.2

New features

  • Added ability to join and compare cursor content by specific columns (PK/UK) (#453)
  • Added support for comma separated list of suite paths/packages when calling ut.run (#479)
  • Added ability to run a test package that got invalidated due to dependency invalidation (#489)
  • Added support for package level constants and predefined exceptions in --%throws annotation (#685)
  • Added support for standalone --%beforeall, --%beforeeach, --%afterall, --%aftereach annotations with list of procedures to execute (#649)
  • Added support for list of procedure names in before/after annotations (#649)
  • Added support for BLOB/CLOB in is_empty() matcher (#707)

Enchancements

  • utPLSQL will now provide additional warnings, when unsupported annotations are found in a unit test suite package (#624)
  • utPLSQL will now produce valid XML in UT_JUNIT_REPORTER when dbms_output or test results contain <![CDATA[ text (#643)
  • improved installation process for non-DBA users (#658)
  • added uninstall_all.sql script that completely removes utPLSQL objects (#673)
  • Changed the way contexts are named (#674)
  • Added ability to pass client encoding information for XML/HTML reporting (requires utPLSQL-cli 3.1.1) (#676)
  • Exposed base objects for expectations, so that IDE like DataGrip can provide auto-complete (#675)
  • Both context-name as well as procedure inside context can now be passed as parameter to ut.run() (#679)
  • Added validation of privileges before installation of utPLSQL (#693)

Bug-fixes

  • UT_JUNIT_REPORTER does not report tests when procedure names are not all lower-case (#659) (#696)
  • Fixed utPLSQL installation order to avoid warnings/failures on install (#657)
  • Fixed uninstall process for utPLSQL (#673)
  • Fixed syntax errors in HTML coverage report (#681) (#682)
  • Fixed install requirements documentation (#687)
  • Fixed capturing of DBMS_OUTPUT buffer at the start of test run (#686)

Internal enhancements

  • Added continuous testing of XML/HTML reports format (#684)
  • Added sonarcloud branch-based and PR code analysis (#708)
  • Added ability to trigger builds on sub-projects (#501)