Skip to content

utplsql-core

utPLSQL v3.0.2 - released

utPLSQL v3.0.2 - released

Changes in this release

Documentation

  • Documentation now refers to migration project
  • Documentation now refers to a valid object name: ut_file_mapping
  • Install and Uninstall scripts are now much more readable
  • Install guide now provides snippet on how to download latest release on Windows

Installation

  • Added override user/password/tablespace for install_headless
  • Installation is now smooth even if profiler tables already exist

Internal improvements

  • Improved reporting from RunTest
  • Fixed publishing of release documentation history

Improvements and fixes

  • Fixed rare issue with ORA-22813: operand value exceeds system limits
  • Stack trace is now properly parsed on all machines
  • The --%disabled annotation on suite level is now reporting all tests as disabled
  • Coverage reporting is now properly filtering test packages on that use suitepath
  • Line of code for failed expectation is now also shown for unit tests owned by other users
  • Line no of failed test is now properly reported when using ut.fail
  • Annotation parameter list can now have spaces before/after brackets
  • Warnings in documentation reporter are now properly numbered
  • Documentation reporter is now providing a timing information for each test
  • by xUnit reporter now displays name of the package/procedure if suite/test has no description
  • Fixed errors with multi-byte characters in conversion from/to clob

utPLSQL v3.0.1 - released

utPLSQL v3.0.1 - released

Issues solved in the release

  • Suite/test description now support commas and inner closing brackets
  • Failure message when comparing different datatypes was improved
  • Users, packages and procedures with $ and # in the name are now supported
  • Improved reporting on the line of the expectation failed in the test procedure
  • Fixed but with multibyte character sets
  • Fixed prompts for install of synonyms bug
  • Fixed HTML Coverage reporting on schema

Other changes

  • Add MD5 checksum to releases
  • Fix deployment to gh-pages branch on TAG bug
  • Small issues in the documentation

utPLSQL v3.0.0 - released!

First official release of fully rewritten utPLSQL.

Key features

  • Compatible with and tested on Oracle 11.2, 12.1 and 12.2
  • multiple ways to compare data with matchers
  • native comparison of complex types (objects/collections/cursors)
  • in-depth and consistent reporting of failures and errors for tests
  • tests identified and configured by annotations
  • hierarchies of test suites configured controlled by annotations
  • automatic (configurable) transaction control using annotations
  • Build-in coverage reporting
  • Integration with SonarQube, Coveralls, Jenkins and Teamcity using reporters
  • plugin architecture for reporters and matchers
  • flexible and simple test invocation
  • multi-reporting and test real-time progress test-run from using utPLSQL-sql-cli

Version v3.0.0-beta has been released

Version 3 has reached beta state.

It can be downloaded from the releases page.

It's being used now in multiple organizations with great success. The documentation work is progressing. However, we realize that quite a bit of work needs to be done in this area.

We welcome support requests and discussions, feature requests, and bug reports in the GitHub issues log.

This is not an April Fools Day Joke, we really release it.

Version 3.0.0.0-Alpha1 released

Version 3 has reached alpha state.

It can be downloaded from the releases page.

It's being used now in multiple organizations with great success. The documentation work is progressing. However, we realize that quite a bit of work needs to be done in this area.

We welcome support requests and discussions, feature requests, and bug reports in the GitHub issues log.

Version 3 - pre-alpha

Version 3 in pre-alpha state

Work on version 3 of utPLSQL has been moving quickly.
Nearly every day version 3 has commits to repository with multiple developers contributing.

It won't be long until we are in an alpha status. If your interested in following along or helping out with the project check out the version 3 readme.md

We welcome support requests and discussions, feature requests, and bug reports in the GitHub issues log.