Deploy to gh-pages branch: base commit 58f69979f8676aa1808b09ff09af30aa9f9e6f9d

github-actions[bot] · github-actions[bot] · commit d6d9b52dce80 · 2022-04-23T10:47:43.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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Introduction to 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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Annotations
 
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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Best Practices
 
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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Coverage
 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.
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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Exception handling and reporting
 
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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Expectation concepts 
 Validation of the code under test (the tested logic of procedure/function etc.) is performed by comparing the actual data against the expected data.
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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Qyerying for test suites
 
@@ -39,6 +39,16 @@ To get a full information about suite `TEST_STUFF` including suite description,
 select * from table(ut_runner.get_suites_info(USER, 'TEST_STUFF')) where item_type = 'UT_TEST';
 ```
 
+To get a full information about suites that have a path like  `ut3:tests.test_package_*` including suite description, all contexts and tests in a suite 
+```sql
+select * from table(ut_runner.get_suites_info('ut3:tests.test_package_*') where item_type = 'UT_TEST';
+```
+
+To get a full information about suites that have object name like  `test_package_*` including suite description, all contexts and tests in a suite 
+```sql
+select * from table(ut_runner.get_suites_info('test_package_*'));
+```
+
 ## Checking if schema contains tests
 
 Function `ut_runner.has_suites(a_owner)` returns boolean value indicating if given schema contains test 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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Running tests
 
@@ -45,6 +45,9 @@ The **functions** can only be used in SELECT statements. They execute the specif
 ## ut.run procedures
 
 The examples below illustrate different ways and options to invoke `ut.run` procedures.
+You can use a wildcard character `*` to call tests by part of their name or to call tests that are located on paths matched by part of path string.
+Wildcard character can be placed anywhere on the path and can occur mutliple times.
+Schema name cannot contain a wildcard character whether is in a suitepath call or call by object name.
 
 ```sql
 alter session set current_schema=hr;
@@ -75,6 +78,23 @@ end;
 Executes all tests from all packages that are on the _com.my_org.my_project_ suitepath.
 Check the [annotations documentation](annotations.md) to find out about suitepaths and how they can be used to organize test packages for your project.
 
+```sql
+set serveroutput on
+begin
+  ut.run('hr:com*');
+end;
+```
+
+Executes all tests in schema `hr` from all packages that are on suitepath starting with `com`.
+
+```sql
+set serveroutput on
+begin
+  ut.run('hr:co*.my_*.my_*');
+end;
+```
+
+Executes all tests in schema `hr` from all packages that starting with `my_` and all tests starting with `my_*` that are on suitepath starting with `co` .
 
 ```sql
 set serveroutput on
@@ -124,6 +144,22 @@ Using a list of items to execute allows you to execute a fine-grained set of tes
 
 List can be passed as a comma separated list or a list of *ut_varchar2_list objects* or as a list within ut_varchar2_list.
 
+```sql
+set serveroutput on
+begin
+  ut.run('hr.test*');
+end;
+```
+Executes all tests in schema `hr` located in packages starting with name `test`.
+
+```sql
+set serveroutput on
+begin
+  ut.run('hr.test_apply_bonus.bonus_*');
+end;
+```
+Executes test procedures with names starting with `bonus` in package `hr.test_apply_bonus` .
+
 
 **Note:**
 
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.4003--develop-blue.svg)
+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)
 
 # Upgrading from version 2
 
diff --git a/utPLSQL/index.md b/utPLSQL/index.md
@@ -5,7 +5,7 @@ layout: default
 # Documentation
 
  - [Latest v3.1.12 documentation](latest/) - Created 25 Feb 2022 - 12:47:56 AM
- - [Latest development version](develop/) - Created 15 Apr 2022 - 10:19:18 PM
+ - [Latest development version](develop/) - Created 23 Apr 2022 - 10:47:42 AM
 
 ## Documentation release 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.4003--develop-blue.svg)`
	`1`	`+![version](https://img.shields.io/badge/version-v3.1.13.4014--develop-blue.svg)`
`2`	`2`
`3`	`3`	`### utPLSQL v3 Major Contributors`
`4`	`4`