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 — Debug utPLSQL test · Issue #87 · utPLSQL/utPLSQL-SQLDeveloper

Debug utPLSQL test #87

New issue
Copy link
New issue
Copy link
Closed
#106
Closed
Debug utPLSQL test#87
#106
Copy link
Assignees
PhilippSalvisberg
Labels
enhancement
Milestone
v1.2.0

Description

@PhilippSalvisberg
PhilippSalvisberg
opened on Aug 25, 2019
Issue body actions

Current Behavior

In version 1.1.0 you can run utPLSQL tests. But if you want to debug a utPL/SQL test, some manual steps are involved. There are several ways to do that.

One way is to run a utPLSQL test in a worksheet change the code to a simple anonymous PL/SQL block (no SQL*Plus statements are allowed) to enable the Debug... context menu option and then select this menu option to launch the debugger.

Example

1. Launch Debugger

utplsql_1_launch_debugger

2. Debugging Session

utplsql_2_debugging_session

Expected Behavior

Launch the Debugger directly

  1. From the context menu of the Database Connections navigator tree, for one or multiple selected nodes for which a "Run utPLSQL test" menu item is available in v1.1.0.

  2. From the Worksheet or PL/SQL editor via context menu, when the "Run utPLSQL test" menu item is available in v1.1.0.

  3. From the Realtime Reporter via toolbar.

  4. From the Realtime Reporter via context menu on the overview table for the selected test(s).

Out of Scope

The following is not in scope of the utPLSQL for SQL Developer extension. At least they are not considered part of this issue.

Managing Breakpoints

Breakpoints need to be set in advance or during the debugging session.

Compiling PL/SQL Code for Debug

This needs to be done before starting a debug session. Either for chosen components via SQL Developer or via a script recompiling all relevant code for debug.

Activity

  1. PhilippSalvisberg
    added
    enhancement
    on Aug 25, 2019
  2. PhilippSalvisberg
    added this to the v1.2.0 milestone on Aug 25, 2019
  3. PhilippSalvisberg
    self-assigned this
    on May 30, 2020
  4. PhilippSalvisberg
    closed this as completedin #106on Jun 2, 2020
  5. PhilippSalvisberg
    added a commit that references this issue on Jun 2, 2020

    Merge pull request #106 from utPLSQL/feature/issue-87-debug

    c2b746d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @PhilippSalvisberg
    PhilippSalvisberg

Labels

enhancement

Type

No type

Projects

No projects

    Milestone

    • v1.2.0

    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.