diff --git a/.github/workflows/build_pages.yml b/.github/workflows/build_pages.yml deleted file mode 100644 index 5b9353e..0000000 --- a/.github/workflows/build_pages.yml +++ /dev/null @@ -1,23 +0,0 @@ -# Based on: https://blog.elmah.io/deploying-a-mkdocs-documentation-site-with-github-actions/ -name: build -on: - push: - branches: - - main -jobs: - deploy: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v4 - with: - fetch-depth: 0 - - uses: actions/setup-python@v2 - with: - python-version: 3.x - - name: Setup MkDocs - run: | - pip install mkdocs-material - pip install mkdocs-git-revision-date-localized-plugin - pip install mike - - name: Build website - run: mkdocs gh-deploy --verbose diff --git a/.gitignore b/.gitignore deleted file mode 100644 index fbb1c11..0000000 --- a/.gitignore +++ /dev/null @@ -1,6 +0,0 @@ -_site -.sass-cache -.jekyll-metadata -.idea -/.jekyll-cache/ -/Gemfile.lock diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 diff --git a/404.html b/404.html new file mode 100644 index 0000000..a6e2fac --- /dev/null +++ b/404.html @@ -0,0 +1,1707 @@ + + + +
+ + + + + + + + + + + + + + + + +Welcome to the new utPLSQL website. We are still in the early stages of moving to GitHub.
+The Code has already been moved.
+The following still needs to be done:
+ + + + + + + + + + + + + + + + + + + + + + + +Issue #19 to link documentation to the website has been completed.
+Issue #4 to update all URL sourceforge References to GitHub, has also been completed.
+You can visit the Documentation by using the menu item at the top of the page.
+ + + + + + + + + + + + + + + + + + + + + + +Version 2.3.1 has been released.
+This release updates documentation to reflect the move of the project to GitHub.
+Current and past releases can be located on our downloads page.
+ + + + + + + + + + + + + + + + + + + + + + +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
+Feel free to join us in our slack chat room where we communicate daily about the project.
+We welcome support requests and discussions, feature requests, and bug reports in the GitHub issues log.
+ + + + + + + + + + + + + + + + + + + + + + +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.
+Feel free to join us in our slack chat room where we communicate daily about the project.
+We welcome support requests and discussions, feature requests, and bug reports in the GitHub issues log.
+ + + + + + + + + + + + + + + + + + + + + + +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.
+Feel free to join us in our slack chat room where we communicate daily about the project.
+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.
+ + + + + + + + + + + + + + + + + + + + + + +Key features
+utPLSQL v3.0.1 - released
+utPLSQL v3.0.2 - released
+Changes in this release
+ut_runner.run
ut_expectation
sub-typesYou may find the client on the download page
+Both driver files need to be downloaded and placed in utPLSQL-cli/lib
folder
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
+ + + + + + + + + + + + + + + + + + + + + + +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-cli
is no longer supported. +UseutPLSQL-cli
release 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_reporter
ut_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 DISABLED
utPLSQL-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)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)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 How to easily integrate @utPLSQL into @VisualStudio via External Tools.
+ + + + + + + + + + + + + + + + + + + + + + + + +ut_runner.is_test
#788ut_runner.is_suite
#787ut_runner.has_suites
#786ANY
grants #737 --%context
with --%displayname
#726to_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 #806v3.1.5
¶3.1.5
where to_equal
matcher was failing due to privileges when comparing non sql diffable types #870This 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.
+-q, --quiet
parameter-d, --debug
parameterutplsql run "sys as sysdba"/pw@connectstring
(#115)-t, --timeout
parameter (#124)/
and passwords containing @
by encapsulating those in the connectstring with "
: utplsql run "my/User"/"P@ssword"@server:1521/Service
(#111)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.
+
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.
+ + + + + + + + + + + + + + + + + + + + + + +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.
+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.
+
## New features
+json
in Oracle 12.2 and above #924tag
annotation to enable tagging of tests and suites #66## Enhancements
+dbms_utility.name_resolve
#569 #885## Bug fixes
+ut_realtime_reporter
missing warnings in test and suite output structures #936join_by / exclude / include
invalid syntax on collection in anydata compare #912ut_junit_reporter
producing invalid output on failing tests with long failure message #927ut_sonar_test_reporter
producing invalid output on failing tests with long failure message #925ut_coverage_cobertura_reporter
producing wrong line breaks which breaks the xml validation against DTD #917exclude
option for ref cursor where column order was not resolved correctly #911unordered
option for ref cursor with null values #914ORA-00907
when comparing ref cursors with BINARY_ columns #899to_be_like
in Oracle Database 11.2.0.4 due to Oracle Bug 14402514 #891## Documentation improvements
+## Internal enhancements
+ + + + + + + + + + + + + + + + + + + + + + + +-f=ut_documentation_reporter -o="output.txt"
you will have to enclose the "output.txt" part as shown--tags=tag1[,tag2[,tag3]]
parameter (#157)-r
/--random-test-order
and -seed
/--random-test-order-seed
(#139)-D
/--dbms_output
(#137)orai18n.jar
is not on the classpath. This is highly recommended due to some strange behaviour of the jdbc-driver otherwise (#146, #153)-type_mapping
) parameter is now interpreted correctly (#143)CompatibilityProxy
assumedUtPlsql
version. This replaces the former skipCompatibilityCheck
parametergetDatabaseVersion
is now deprecated in favor of getUtPlsqlVersion
and getRealDbPlsqlVersion
TestRunner
getOptions
returns the current TestRunnerOptions
nowhttps://packagecloud.io/utPLSQL/utPLSQL-java-api/packages/java/org.utplsql/java-api-3.1.7.jar
+<dependency>
+ <groupId>org.utplsql</groupId>
+ <artifactId>java-api</artifactId>
+ <version>3.1.7</version>
+</dependency>
+
We just added a new section to our website: Resources.
+We will keep adding all kinds of examples, tutorials, videos, blog posts and other stuff related to +utPLSQL to this page, but we might not know everything.
+So please, if you find something related to utPLSQL which is publicly (without a paywall) available or if you created something +yourself, please let us know!
+ + + + + + + + + + + + + + + + + + + + + + +--%name
to allow for providing custom name for contexts #1016The value of --%context
annotation is no longer representing context name
.
+This value is now context description (displayname).
+With this change, the --%context
annotation is now aligned with --%test
and --%suite
annotation syntax.
New annotation --%name
was introduced to facilitate naming of contexts.
--%throws
annotations at runtime #721 #1033Download v3.1.10
release version here
Happy new year! Thanks to Simon Martinelli utPLSQL v3+ is now integrated with PL/SQL Developer IDE
+See details of plugin usage in readme file
+PlsqlDeveloperUtPlsqlPlugin.dll
or PlsqlDeveloperUtPlsqlPlugin_x86.dll
to the PlugIns directory of your PL/SQL Developer installationDownload v3.1.11
release version here
--%disabled
annotation. See documentation. Implemented in: #1183, resolves #610.JSON
datatype on Oracle 21c
. Implemented in #1181, resolves #1114.to_be_within( distance|pct ).of_(expoected)
. See documentation. Implemented in #1076, resolves #77.JSON
data. Implemented in #1181, resolves #1113.Download v3.1.12
release version here
a_coverage_schemes
option of utPLSQL by @pesse in #180Today is #JoelKallmanDay.
+As memorial of Joel Kallman, on this day utPLSQL launched its new website using different engine.
+We have moved away from using Jekyll with GitHub Pages to host project and organization sites. +Jekyll was simply too much hussle and we used MkDocs to generate offline documentation for utPLSQL that was packaged into the release zip file.
+So instead of using two different methods, wei will now use only one. MkDocs is now used for both utPSLQL offline and for online organization and project pages.
+Thanks to wonderful material theme and mike(versioning plugin) for MkDocs you may now enjoy the following new features:
+Hopefully, you will like the changes and enhancements. All the permanent links to old site should still be working.
+ + + + + + + + + + + + + + + + + + + + + + +Download v3.1.13
release version here
and
and or
operators when running tests by tags by @lwasylow in #1250Full Changelog: v3.1.13...v3.1.14
+utPLSQL is an open-source testing framework for PL/SQL and SQL
+It allow for automated testing of:
+utPLSQL is developed 100% voluntarily and embraces a Code of Conduct.
+Feel free to try it out, you won't regret it. +Additional information can be found in the documentation pages.
+While the framework exists since 1999, the current version 3 got completely rewritten in 2016 by passionate members of +the community, using the object-oriented capabilities of the Oracle database to make it more consistent with other +*Unit frameworks (e.g. JUnit for Java).
+This had significant impact on the syntax and the way the framework can be used.
+Name | +Comments | +
---|---|
Jacek Gebal | +Project lead | +
Pavel Kaplya | ++ |
Samuel Nitsche | ++ |
Lukasz Wasylow | ++ |
Philipp Salvisberg | ++ |
Many thanks to all the contributors.
+Name | +Comments | +
---|---|
Robert Love | ++ |
David Pyke | ++ |
Vinicius Avellar | ++ |
Name | +Comments | +
---|---|
Steven Feuerstein | +Original Author | +
Chris Rimmer | ++ |
Patrick Barel | ++ |
Paul Walker | ++ |
The utPLSQL project is community-driven and is not commercially motivated. Nonetheless, donations and other contributions are always welcome, and are detailed below.
+![]() |
+utPLSQL has been supported by Redgate in the form of sponsored stickers and t-shirts. Thank you for helping us spreading the word! | +
{"use strict";/*!
+ * escape-html
+ * Copyright(c) 2012-2013 TJ Holowaychuk
+ * Copyright(c) 2015 Andreas Lubbe
+ * Copyright(c) 2015 Tiancheng "Timothy" Gu
+ * MIT Licensed
+ */var Va=/["'&<>]/;qn.exports=za;function za(e){var t=""+e,r=Va.exec(t);if(!r)return t;var o,n="",i=0,s=0;for(i=r.index;i