René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Extend ut_realtime_reporter to include disabled reason","articleBody":"## Is your feature request related to a problem? Please describe\r\n\r\nIn utPLSQL v3.1.12 a feature was added to add a reason for a disabled test. See PR #1183 and issue #610. Some reporters were extended, but this information is missing in `ut_realtime_reporter`. The utPLSQL runner for SQL Developer and PL/SQL Developer are using the `ut_realtime_reporter`. So this reporter should include the reason for a disabled test. This is a prerequisite to display the information in the UI.\r\n\r\n## Describe the solution you'd like\r\n\r\nAdd the node `disabledReason` in the `test` node that is produced in [`before_calling_run`](https://github.com/utPLSQL/utPLSQL/blob/v3.1.12/source/reporters/ut_realtime_reporter.tpb#L45). Use CamelCase as in other nodes of this reporter. Examples: `executableType`, `ownerName`, `objectName` and `procedureName`. \r\n\r\n## Describe alternatives you've considered\r\n\r\nSnake-case naming of the node `disable_reason` as suggested by @jgebal in utPLSQL/utPLSQL-PLSQL-Developer#25 . The naming would be inconsistent with the other nodes in the `ut_realtime_reporter`. Therefore I strongly suggest to use CamelCase for this additional node. I suggest to use `disabledReason`.\r\n\r\n## Additional context\r\n\r\nThe UI related issues are utPLSQL/utPLSQL-PLSQL-Developer#25 and utPLSQL/utPLSQL-SQLDeveloper#143 .\r\n","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2022-02-25T14:33:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1192/utPLSQL/issues/1192"}