Title: Debug utPLSQL test · Issue #87 · utPLSQL/utPLSQL-SQLDeveloper · GitHub
Open Graph Title: Debug utPLSQL test · Issue #87 · utPLSQL/utPLSQL-SQLDeveloper
X Title: Debug utPLSQL test · Issue #87 · utPLSQL/utPLSQL-SQLDeveloper
Description: 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 ...
Open Graph Description: 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...
X Description: 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...
Opengraph URL: https://github.com/utPLSQL/utPLSQL-SQLDeveloper/issues/87
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Debug utPLSQL test","articleBody":"# Current Behavior\r\n\r\nIn 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. \r\n\r\nOne 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. \r\n\r\n## Example\r\n\r\n### 1. Launch Debugger\r\n\r\n\r\n\r\n### 2. Debugging Session\r\n\r\n\r\n\r\n# Expected Behavior\r\n\r\n## Launch the Debugger directly\r\n\r\n1. 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.\r\n\r\n2. From the Worksheet or PL/SQL editor via context menu, when the \"Run utPLSQL test\" menu item is available in v1.1.0.\r\n\r\n3. From the Realtime Reporter via toolbar.\r\n\r\n4. From the Realtime Reporter via context menu on the overview table for the selected test(s).\r\n\r\n## Out of Scope\r\n\r\nThe following is not in scope of the utPLSQL for SQL Developer extension. At least they are not considered part of this issue.\r\n\r\n### Managing Breakpoints\r\n\r\nBreakpoints need to be set in advance or during the debugging session. \r\n\r\n### Compiling PL/SQL Code for Debug\r\n\r\nThis 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.","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2019-08-25T08:32:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/87/utPLSQL-SQLDeveloper/issues/87"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:07533881-50f0-4d7d-2de6-e8ae63d41140 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E65C:16B518:86BB9F:B57E30:69692DE5 |
| html-safe-nonce | 5892322f600fb037ab008193f6630b0927fc74398501efe4d426ea6bd21720c9 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNjVDOjE2QjUxODo4NkJCOUY6QjU3RTMwOjY5NjkyREU1IiwidmlzaXRvcl9pZCI6IjY0NjEwMzEyODc4MjM2MDkzMTciLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 52dcd79cd49ccaeb280892b3acb0fa4b3461919447ad20d8bc8b246336b27cad |
| hovercard-subject-tag | issue:484905430 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/utPLSQL/utPLSQL-SQLDeveloper/87/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d68bf0de7e290dc887257d30589b57fa209f28a5b6bc1c2d1c4d606976084802/utPLSQL/utPLSQL-SQLDeveloper/issues/87 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d68bf0de7e290dc887257d30589b57fa209f28a5b6bc1c2d1c4d606976084802/utPLSQL/utPLSQL-SQLDeveloper/issues/87 |
| og:image:alt | 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... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | PhilippSalvisberg |
| hostname | github.com |
| expected-hostname | github.com |
| None | 54182691a21263b584d2e600b758e081b0ff1d10ffc0d2eefa51cf754b43b51d |
| turbo-cache-control | no-preview |
| go-import | github.com/utPLSQL/utPLSQL-SQLDeveloper git https://github.com/utPLSQL/utPLSQL-SQLDeveloper.git |
| octolytics-dimension-user_id | 15661281 |
| octolytics-dimension-user_login | utPLSQL |
| octolytics-dimension-repository_id | 111097428 |
| octolytics-dimension-repository_nwo | utPLSQL/utPLSQL-SQLDeveloper |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 111097428 |
| octolytics-dimension-repository_network_root_nwo | utPLSQL/utPLSQL-SQLDeveloper |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | d69ac0477df0f87da03b8b06cebd187012d7a930 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width