Skip to content

Commit 1a89a53

Browse files
author
Jacek Gębal
committed
Update cli release announcement
1 parent a3c341c commit 1a89a53

1 file changed

Lines changed: 34 additions & 0 deletions

File tree

‎docs/announcements/posts/2026/2026-10-17-cli-version3.2.2-released.md‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,40 @@ categories:
88
- "utplsql-cli"
99
---
1010

11+
## Highlights
12+
13+
### Code coverage scope defined with regular expressions
14+
15+
`utplsql run` has four new options that decide what is included in the coverage report by schema or object **name pattern**:
16+
17+
<!-- more -->
18+
| Option | Meaning |
19+
|-------------------------|--------------------------------------------------------------------|
20+
| `-include-schema-expr` | report coverage only on schemas whose name matches the expression |
21+
| `-exclude-schema-expr` | leave out schemas whose name matches the expression |
22+
| `-include-object-expr` | report coverage only on objects whose name matches the expression |
23+
| `-exclude-object-expr` | leave out objects whose name matches the expression |
24+
25+
When project files are mapped to database objects (`-source_path` / `-test_path`), coverage is already limited to those files.
26+
The new options are for code that cannot be mapped to project files. They allow for new packages that follow your naming conventions
27+
to be covered (or left out) automatically, without updating a list of schemas or objects in your pipeline.
28+
29+
```bash
30+
utplsql run app/pass@db -p=app -f=ut_coverage_html_reporter -o=coverage.html \
31+
-include-schema-expr='^APP_' -exclude-schema-expr='_TEST$' -exclude-object-expr='_TMP$'
32+
```
33+
34+
- Expressions are case-insensitive Oracle regular expressions. Object expressions are matched against the object name without the schema.
35+
- If an include expression is given, `--coverage-schemes` and `-include` are ignored. All exclude options are always applied.
36+
- The filters do not apply when coverage is gathered on project files (`-source_path` / `-test_path`).
37+
38+
See [Filtering objects in coverage reports](https://www.utplsql.org/utPLSQL/latest/userguide/coverage.html#filtering-objects-in-coverage-reports)
39+
and the [utPLSQL-cli documentation](https://www.utplsql.org/utPLSQL-cli.html).
40+
41+
The utPLSQL Maven plugin supports the same filters (`includeSchemaExpr`, `excludeSchemaExpr`, `includeObjectExpr`, `excludeObjectExpr`)
42+
and now documents them in detail.
43+
44+
1145
## What's Changed
1246
* Add coverage filter options by regular expression by @jgebal in [#233](https://github.com/utPLSQL/utPLSQL-cli/pull/233)
1347
* Announce releases with the shared announce-release action by @jgebal in [#234](https://github.com/utPLSQL/utPLSQL-cli/pull/234)

0 commit comments

Comments
 (0)