Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Feature - include/exclude objects and schemas by regex #1186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jgebal merged 20 commits into from
Mar 2, 2022
Merged

Feature - include/exclude objects and schemas by regex #1186

Changes from 1 commit
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
0c57a9c
Initial checkin for exclude objects regex.
lwasylow Feb 9, 2022
8370aa9
commit changes
lwasylow Feb 22, 2022
fc7bee9
Merge branch 'develop' of https://github.com/utPLSQL/utPLSQL into fea…
lwasylow Feb 23, 2022
7b9e085
Making more changes
lwasylow Feb 25, 2022
4eec03e
Update to code to address sql injection concerns.
lwasylow Feb 25, 2022
e7d59b4
Splitting skipped framework objects and excluded objects into separat…
lwasylow Feb 25, 2022
6f5b2dc
Update of coverage documentation
jgebal Feb 25, 2022
b430b43
Fixed typo in documentation
jgebal Feb 25, 2022
efa78a3
Merge remote-tracking branch 'origin/develop' into feature/1053_exclu…
jgebal Feb 26, 2022
4ab0f58
Added ability to publish coverage generated by test jobs running utPL…
jgebal Feb 26, 2022
5201f2a
Merge remote-tracking branch 'origin/develop' into feature/1053_exclu…
jgebal Feb 26, 2022
a84246b
Adding extra tests for code coverage
lwasylow Feb 27, 2022
090207c
Added extra coverage for file mapping.
lwasylow Feb 27, 2022
df31fba
g_coverage_run_id is now reset after coverage collection is stopped.
jgebal Feb 27, 2022
0a2f478
Improved coverage collection scope and stability on self-tests for ut…
jgebal Feb 27, 2022
bd05e4c
Coverage documentation improvements.
jgebal Mar 1, 2022
3b9b626
Coverage documentation improvements.
jgebal Mar 1, 2022
3bdb9d0
Fixing flaky test
jgebal Mar 2, 2022
7cca6b4
Update of coverage.md
jgebal Mar 2, 2022
2533638
Update coverage.md
jgebal Mar 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update of coverage documentation
  • Loading branch information
@jgebal
jgebal committed Feb 25, 2022
commit 6f5b2dc81148c7723a1d174992603c5203af1dbd
16 changes: 15 additions & 1 deletion docs/userguide/coverage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -780,6 +780,10 @@ ut_coverage_options(
exclude_objects ut_varchar2_rows := null,
include_objects ut_varchar2_rows := null,
file_mappings ut_file_mappings := null
include_schema_expr varchar2(4000) := null,
include_object_expr varchar2(4000) := null,
exclude_schema_expr varchar2(4000) := null,
exclude_object_expr varchar2(4000) := null
);
```

Expand All @@ -795,11 +799,21 @@ The `a_coverage_options` parameter is used to control the scope and formatting o
- `exclude_objects` - optional - list of object names to exclude from report - data-type `UT_VARCHAR2_ROWS`
- `include_objects` - optional - list of object names to gather coverage on - data-type `UT_VARCHAR2_ROWS`
- `file_mappings` - optional - list of schema names to gather coverage on - data-type `UT_FILE_MAPPINGS`
- `include_schema_expr` - optional - regular expression to match against schema name to include in coverage - data-type `VARCHAR2(4000)`
- `include_object_expr` - optional - regular expression to match against object name to include in coverage - data-type `VARCHAR2(4000)`
- `exclude_schema_expr` - optional - regular expression to match against schema name to exclude in coverage - data-type `VARCHAR2(4000)`
- `exclude_object_expr` - optional - regular expression to match against object name to exclude in coverage - data-type `VARCHAR2(4000)`

`coverage_run_id` parameter identifies a common coverage run. The valid value type for that parameter is RAW(32).
It is recommended to use `sys_guid()` to generate a common, unique identifier for a specific coverage run.
If the identifier is not unique, previous runs of coverage that used the same `coverage_run_id` will be aggregated to the resulting coverage report.

For details on the meaning of `schema_names`, `exclude_objects`, `include_objects`, `file_mappings` see sections above.
Note that data-types of include/exclude/schema lists are different when calling `ut.run` vs. calling `get_report/get_report_cursor`.


The order of priority is for evaluation of include/exclude is as follows.
- if `file_mappings` is specified then all include/exclude parameters are ignored
- else if `..._expr` is specified then include_objects/exclude_objects parameters are ignored
- else if `schema_names` is specified then the coverage is gathered on all object of specified schemas
- else coverage is gathered on all schemas specified in paths passed to run procedure
- if no paths were specified, the coverage is gathered on current schema of the session running the tests