Skip to content

Commit ba6ca3e

Browse files
author
Jacek Gębal
committed
Correct description of coverage filter expressions
An include expression makes the -include list and --coverage-schemes irrelevant, and an exclude expression makes the -exclude list irrelevant. Verified against utPLSQL 3.2.3 (ut_coverage.pkb) and on a real database.
1 parent a29a30c commit ba6ca3e

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

‎README.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,8 @@ The TNS alias used in the connect string must match the alias of the credential
209209
Case-insensitive. Object expressions are matched against the object name without the schema.
210210
Anchor them with `^` and `$`, otherwise any partial match counts.
211211
If an include expression is given, `-include` and `--coverage-schemes` are ignored.
212-
All exclude options are always applied and can be combined.
212+
Schema and object exclude expressions are both applied.
213+
If any exclude expression is given, the `-exclude` list is ignored.
213214
Ignored when `-source_path` is used (file mapping defines the coverage scope).
214215
See https://www.utplsql.org/utPLSQL/latest/userguide/coverage.html#filtering-objects-in-coverage-reports
215216

0 commit comments

Comments
 (0)