GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Extend ut_realtime_reporter to include disabled reason · Issue #1192 · utPLSQL/utPLSQL

Extend ut_realtime_reporter to include disabled reason #1192

New issue
Copy link
New issue
Copy link
Closed
#1193
Closed
Extend ut_realtime_reporter to include disabled reason#1192
#1193
Copy link
Assignees
jgebal
Labels
enhancement
Milestone
v3.1.13

Description

@PhilippSalvisberg
PhilippSalvisberg
opened on Feb 25, 2022
Issue body actions

Is your feature request related to a problem? Please describe

In 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.

Describe the solution you'd like

Add the node disabledReason in the test node that is produced in before_calling_run. Use CamelCase as in other nodes of this reporter. Examples: executableType, ownerName, objectName and procedureName.

Describe alternatives you've considered

Snake-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.

Additional context

The UI related issues are utPLSQL/utPLSQL-PLSQL-Developer#25 and utPLSQL/utPLSQL-SQLDeveloper#143 .

Activity

  1. PhilippSalvisberg
    added
    enhancement
    on Feb 25, 2022
  2. jgebal
    self-assigned this
    on Feb 25, 2022
  3. jgebal
    added this to the 3.1.13 milestone on Feb 25, 2022
  4. jgebal
    closed this as completedin #1193on Feb 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @jgebal
    jgebal

Labels

enhancement

Type

No type

Projects

No projects

    Milestone

    • v3.1.13

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.