utPLSQL · jgebal · Mar 2, 2022 · Feb 9, 2022 · Feb 22, 2022 · Feb 23, 2022
diff --git a/docs/userguide/coverage.md b/docs/userguide/coverage.md
@@ -128,16 +128,43 @@ exec ut.run('unit_test_schema', ut_coverage_html_reporter(), a_coverage_schemes
 
 #### Filtering objects in coverage reports
 
-There are two options that can be used to narrow down the scope of coverage report:
-- `a_include_objects` - list of `[object_owner.].object_name` to be included in the coverage report
+There are six options that can be used to narrow down the scope of coverage report:
+- `a_include_objects` - list of `[object_owner.].object_name` to be included in the coverage report.
 - `a_exclude_objects` - list of `[object_owner.].object_name` to be excluded from the coverage report
-
-You may specify both _include_ and _exclude_ object lists to gain more control over what needs to be included / excluded from the coverage report.
+- `a_include_schema_expr` - string of regex expression of schemas to be included in the coverage report. It will override  `a_include_objects` for example :
+    ```sql
+    a_include_schema_expr => '^ut3_develop',
+    a_include_objects => ut3_develop.ut_varchar2_list( 'ut3_tester_helper.regex_dummy_cov' )
+    ```
+  Will result in showing coverage for all schemas that match regular expression `^ut3_develop` and ignore objectes defined by parameter `a_include_objects`
+
+- `a_include_object_expr` - string of regex expression of objects ( no schema names included ) to be included in the coverage report. It will override `a_include_objects` for example:
+    ```sql
+    a_include_object_expr => 'regex123',
+    a_include_objects => ut3_develop.ut_varchar2_list( 'ut3_tester_helper.regex_dummy_cov' )
+    ```
+  Will result in showing coverage for all objects that name match regular expression `regex123` and ignore objectes defined by parameter `a_include_objects`
+
+- `a_exclude_schema_expr` - string of regex expression of schemas to be excluded from the coverage report. It will override `a_exclude_objects` for example:
+    ```sql
+    a_exclude_schema_expr => '^ut3_tester',
+    a_exclude_objects => ut3_develop.ut_varchar2_list( 'ut3_develop.regex_dummy_cov' )
+    ```
+  Will result in showing coverage for all objects that schema is not matching regular expression `^ut3_tester` and ignore exclusion defined by parameter `a_exclude_objects`
+
+- `a_exclude_object_expr` - string of regex expression of objects to be excluded from the coverage report. It will override `a_exclude_objects` for example
+    ```sql
+    a_exclude_object_expr => 'regex123',
+    a_exclude_objects => ut3_develop.ut_varchar2_list( 'ut3_develop.regex_dummy_cov' )
+    ```
+  Will result in showing coverage for all objects that name is not matching regular expression `regex123` and ignore exclusion defined by parameter `a_exclude_objects`
+
+
+You may specify both _include_ and _exclude_ options to gain more control over what needs to be included / excluded from the coverage report.
 
 The object owner is optional in the object list.
 If you do not provide an object owner, the _include_/_exclude_ list will be considered for every schema used for coverage gathering (as described above).
 
-
 Example: Limiting coverage by object name, for tested code located in the same schema as the unit tests.
 ```sql
 exec ut.run(ut_varchar2_list('user_1','user_2'), ut_coverage_html_reporter(), a_include_objects=>ut_varchar2_list('award_bonus'));