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

Show file tree
Hide file tree
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
Next Next commit
Initial checkin for exclude objects regex.
  • Loading branch information
@lwasylow
lwasylow committed Feb 9, 2022
commit 0c57a9cbb495d7d152e60068b28d21926b1ba7af
11 changes: 7 additions & 4 deletions docs/userguide/coverage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,16 +128,19 @@ 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
- `a_include_schema_expr` - string of regex expression of schemas to be included in the coverage report. It will override `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`
- `a_exclude_schema_expr` - string of regex expression of schemas to be excluded from the coverage report. It will override `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`

You may specify both _include_ and _exclude_ object lists to gain more control over what needs to be included / excluded from the coverage report.
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'));
Expand Down
Loading