8000 Coverage not being reported when comment starts with --%param · Issue #1278 · utPLSQL/utPLSQL · GitHub
[go: up one dir, main page]

Skip to content
Coverage not being reported when comment starts with --%param #1278
Open
@fatihsahin364

Description

@fatihsahin364

I installed utPlSql on my computer. I am currently using Allround PL/SQL Developer. When I add a parameter definition as a comment like this -- %param into my source code (not a test suite package), utplsql checks this package and thinks as a test suite/package and inserts this info into the ut_suite_cache_package table.
When I run the test suite there is no problem. But when I want to see the coverage result, I cannot see the package which contains --%param keywords on the coverage result page. After inspecting ut_suite_manager.save_object_cache procedure, I see the "a_suite_items IS NOT NULL AND a_suite_items.count = 0" if clause but when I check the parameters, the a_suite_items parameter is null when the source code doesn't contain any %suite or others special keywords.
After updating the if clause like this "IF a_suite_items IS NULL OR (a_suite_items IS NOT NULL AND a_suite_items.count = 0) THEN" and compiles my non-test suite package and then runs the test suite, it deletes the related line from the ut_suite_cache_package table and shows the package name correctly on the coverage result page.

@jgebal asked me to open this issue after a short conversation with him on Slack.

version info
v3.1.14.4197
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0