Some annotations are only valid for procedures, while some others are only valid at suite level.
Currently, when we parse annotations we do not report any warnings for incorrect/misplaced annotations.
This leads to some confusion and surprises when a suite/test does not execute or misbehaves.
We should introduce a log_warning mechanism, so that suite builder can give feedback to user on issues encountered.
The warnings should be shown to dbms_output from the main session when using multi-session access (utPLSQL-cli) or at the begining/end of outputs from ut_documentation_reporter.
Some annotations are only valid for procedures, while some others are only valid at suite level.
Currently, when we parse annotations we do not report any warnings for incorrect/misplaced annotations.
This leads to some confusion and surprises when a suite/test does not execute or misbehaves.
We should introduce a
log_warningmechanism, so that suite builder can give feedback to user on issues encountered.The warnings should be shown to dbms_output from the main session when using multi-session access (utPLSQL-cli) or at the begining/end of outputs from
ut_documentation_reporter.