Deploy to gh-pages branch: base commit a552566232bccb28cc266964e49e0057feceb87e

github-actions[bot] · github-actions[bot] · commit 346cb1e40360 · 2022-10-17T08:29:03.000+01:00
diff --git a/utPLSQL/develop/about/authors.md b/utPLSQL/develop/about/authors.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 ### utPLSQL v3 Major Contributors 
 
diff --git a/utPLSQL/develop/about/license.md b/utPLSQL/develop/about/license.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 # Version Information
 
diff --git a/utPLSQL/develop/about/project-details.md b/utPLSQL/develop/about/project-details.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 # utPLSQL Project Details
 
diff --git a/utPLSQL/develop/about/support.md b/utPLSQL/develop/about/support.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 # How to get support
 
diff --git a/utPLSQL/develop/index.md b/utPLSQL/develop/index.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 ## What is utPLSQL
 
diff --git a/utPLSQL/develop/userguide/advanced_data_comparison.md b/utPLSQL/develop/userguide/advanced_data_comparison.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 # Advanced data comparison
 
diff --git a/utPLSQL/develop/userguide/annotations.md b/utPLSQL/develop/userguide/annotations.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 Annotations are used to configure tests and suites in a declarative way similar to modern OOP languages. This way, test configuration is stored along with the test logic inside the test package.
 No additional configuration files or tables are needed for test cases. The annotation names are based on popular testing frameworks such as JUnit.
diff --git a/utPLSQL/develop/userguide/best-practices.md b/utPLSQL/develop/userguide/best-practices.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 The following are best practices we at utPLSQL have learned about PL/SQL and Unit Testing. 
 
diff --git a/utPLSQL/develop/userguide/coverage.md b/utPLSQL/develop/userguide/coverage.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 utPLSQL comes with a built-in coverage reporting engine. The code coverage reporting uses package DBMS_PROFILER (and DBMS_PLSQL_CODE_COVERAGE on Oracle database version 12.2 and above) provided with Oracle database.
 Code coverage is gathered for the following source types:
diff --git a/utPLSQL/develop/userguide/exception-reporting.md b/utPLSQL/develop/userguide/exception-reporting.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 The utPLSQL is responsible for handling exceptions wherever they occur in the test run. utPLSQL is trapping most of the exceptions so that the test execution is not affected by individual tests or test packages throwing an exception.
 The framework provides a full stacktrace for every exception that was thrown. The stacktrace is clean and does not include any utPLSQL library calls in it.
diff --git a/utPLSQL/develop/userguide/expectations.md b/utPLSQL/develop/userguide/expectations.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 ## Expectation concepts 
 
diff --git a/utPLSQL/develop/userguide/getting-started.md b/utPLSQL/develop/userguide/getting-started.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 # Getting started with TDD and utPLSQL
 
diff --git a/utPLSQL/develop/userguide/install.md b/utPLSQL/develop/userguide/install.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 ## Supported database versions
 
diff --git a/utPLSQL/develop/userguide/querying_suites.md b/utPLSQL/develop/userguide/querying_suites.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 ## Obtaining information about suites 
 
diff --git a/utPLSQL/develop/userguide/reporters.md b/utPLSQL/develop/userguide/reporters.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 utPLSQL provides the following reporting formats.
 
diff --git a/utPLSQL/develop/userguide/running-unit-tests.md b/utPLSQL/develop/userguide/running-unit-tests.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 utPLSQL framework provides two main entry points to run unit tests from within the database: 
 
diff --git a/utPLSQL/develop/userguide/upgrade.md b/utPLSQL/develop/userguide/upgrade.md
@@ -1,4 +1,4 @@
-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)
 
 # Upgrading from version 2
 
diff --git a/utPLSQL/index.md b/utPLSQL/index.md
@@ -5,7 +5,7 @@ layout: default
 # Documentation versions
 
 
- - [Latest development version](develop/) - Created 14 Oct 2022 - 09:22:23 PM
+ - [Latest development version](develop/) - Created 17 Oct 2022 - 08:29:03 AM
 
 ## Released Version Doc History
 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-![version](https://img.shields.io/badge/version-v3.1.13.4041--develop-blue.svg)`
	`1`	`+![version](https://img.shields.io/badge/version-v3.1.13.4049--develop-blue.svg)`
`2`	`2`
`3`	`3`	`### utPLSQL v3 Major Contributors`
`4`	`4`