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

Skip to content

Regression in 3.1.11 - coverage reporting functionality #1178

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

Jump to bottom
Closed
jgebal opened this issue Jan 16, 2022 · 1 comment
Closed

Regression in 3.1.11 - coverage reporting functionality #1178

jgebal opened this issue Jan 16, 2022 · 1 comment

Comments

@jgebal
Copy link
Member

jgebal commented Jan 16, 2022 •
edited
Loading

utPLSQL introduced regression in that coverage reporting doesn't allow doe exclusion/inclusion of coverage files anymore.
This was caught by a utPLSQL-cli test and is clearly not properly covered by utPLSQL self-testing.

The problem can be seen here:
https://github.com/utPLSQL/utPLSQL-cli/runs/4833244766?check_suite_focus=true

The documentation for how it should work can be found here:
https://github.com/utPLSQL/utPLSQL/blob/develop/docs/userguide/coverage.md#filtering-objects-in-coverage-reports
@jgebal jgebal changed the title Regression 3.1.11 coverage reporting functionality Regression in 3.1.11 - coverage reporting functionality Jan 16, 2022
@jgebal
Copy link
Member Author

jgebal commented Jan 16, 2022

Upon investigation I've realised the framework works OK. The problem was with how a test was checking outputs from coverage report.
The format of report was changed in 3.1.11 to include object type and address the issue: #1086
A change was done to enhance the regular expression used in the test and then the regex group used to check results

@jgebal jgebal closed this as completed Jan 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jgebal