v3.1.53.1.5 where to_equal matcher was failing due to privileges when comparing non sql diffable types #870v3.1.43.1.4 where to_be_empty matcher was failing due to privileges #864to_contain matcher for collections and cursors #79unordered_columns (uc) option for cursor comparison to ignore the order of the columns #779 ut_debug_reporter for debug logging #480 ut_realtime_reporter for utPLSQL-SQLDeveloper extension #795ut_output_buffer #840get_reporters_list function #814dbms_lock.sleep to dbms_session for newer DB versions #806ut_runner.is_test #788ut_runner.is_suite #787ut_runner.has_suites #786ANY grants #737 --%context with --%displayname #726How to easily integrate @utPLSQL into @VisualStudio via External Tools.
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.
utplsql info [user/password@connectstring] #77 utplsql reporters user/password@connecstring ALTER SESSION statements when connecting #101 ut.run (#479)--%throws annotation (#685)--%beforeall, --%beforeeach, --%afterall, --%aftereach annotations with list of procedures to execute (#649)is_empty() matcher (#707)<![CDATA[ text (#643)uninstall_all.sql script that completely removes utPLSQL objects (#673)ut.run() (#679)On April 25th, a major release 3.1.0 of utPLSQL was published on github and the information was not published on our site.
Right after the release two issues were found resulting in bug fixes and release 3.1.1
utplsql-cli and idle time exceeds 1 minute (https://github.com/utPLSQL/utPLSQL/issues/652)Important Notice
Starting with this release,
utPLSQL-sql-cliis no longer supported. UseutPLSQL-clirelease 3.1.0 or above to interact with this and upcoming versions of utPLSQL.
ut_tfs_junit_reporter for MS Team Foundation Server to support old JUnit xml formatut_coverage_cobertura_reporterut_xunit_reporter. The reporter now conforms to the format specification.ut_junit_reporter as a base for ut_xunit_reporter. The ut_xunit_reporter remains active for backward compatibility but is considered depreciatedut_documentation_reporter to display tests annotated--%disabled as DISABLEDutPLSQL-java-api without code changesthrows annotation to simplify writing tests for code that throws an exceptioncontext to enable grouping of tests into sub-suite in a test suite packagehave_count matcher for checking cursor rows/collection elements countinclude() and exclude() extensions to cursor and object/collection data comparisondiff functionality for cursor, object and collection data ut.expect() on closed cursor (#548)Existing state of packages was discarded/invalidated exceptions (ORA-04068/ORA-04061). The whole suite will execute, test result reports will be available and the exception will be re-thrown to the user after the run was finished. (#504)a_include_objects (#511)--%suite and procedure-specific annotations. (#514 / #516)end loop elements (#539)xunit_reporter (#547)ORA-00001: unique constraint (UTP3.UT_COVERAGE_SOURCES_TMP_PK) violated (#568)Both driver files need to be downloaded and placed in utPLSQL-cli/lib folder
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.
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
For more info on improvements and fixes, check out the blog post from Samuel Nitsche
You may find the client on the download page
Both driver files need to be downloaded and placed in utPLSQL-cli/lib folder