Title: Run utPLSQL tests in a dedicated utPLSQL view · Issue #6 · utPLSQL/utPLSQL-SQLDeveloper · GitHub
Open Graph Title: Run utPLSQL tests in a dedicated utPLSQL view · Issue #6 · utPLSQL/utPLSQL-SQLDeveloper
X Title: Run utPLSQL tests in a dedicated utPLSQL view · Issue #6 · utPLSQL/utPLSQL-SQLDeveloper
Description: In version 0.1 all utPLSQL tests are executed as script in a SQL Developer worksheet and the test output is shown in the script output pane. This was easy to implement and is an acceptable solution for a MVP but it has the following flaw...
Open Graph Description: In version 0.1 all utPLSQL tests are executed as script in a SQL Developer worksheet and the test output is shown in the script output pane. This was easy to implement and is an acceptable solution...
X Description: In version 0.1 all utPLSQL tests are executed as script in a SQL Developer worksheet and the test output is shown in the script output pane. This was easy to implement and is an acceptable solution...
Opengraph URL: https://github.com/utPLSQL/utPLSQL-SQLDeveloper/issues/6
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Run utPLSQL tests in a dedicated utPLSQL view","articleBody":"In version 0.1 all utPLSQL tests are executed as script in a SQL Developer worksheet and the test output is shown in the script output pane. This was easy to implement and is an acceptable solution for a [MVP](https://en.wikipedia.org/wiki/Minimum_viable_product) but it has the following flaws:\r\n\r\n- DBMS_OUTPUT is produced after all tests have been completed. The developer does not see the progress\r\n- When a test fails, the developer has to navigate manually to the failing source code line (no hyperlink available)\r\n- Results are produced in black and white colors only, there is no \"green bar\" indicated a successful test execution\r\n- Overall it looks and feels awkward and it is less fun for the developer to work with\r\n\r\nTo address these flaws all tests should be executed by the utPLSQL extension (without blocking the current connection) and the results should be presented in a dedicated utPLSQL view. This view should look similar to the JUnit view in Eclipse.\r\n\r\n\r\n\r\n\r\n\r\n\r\n","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2018-01-27T21:46:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/6/utPLSQL-SQLDeveloper/issues/6"}
| 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:b04c4f66-f38b-87b5-4abb-9e4bbde207bf |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | DB36:22DB0A:1C20A3F:27502AA:69692DFA |
| html-safe-nonce | bd33e0235a6d1d29c1c92a3567b038eb71da722424eb542b9107a2a16d831b74 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEQjM2OjIyREIwQToxQzIwQTNGOjI3NTAyQUE6Njk2OTJERkEiLCJ2aXNpdG9yX2lkIjoiNTUwMTgxODMxMDExOTQ2ODUzOCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 8f1b11626c108b51aee5ebca7944b9d93bce5c6829b7308ef5116563ec19d2a4 |
| hovercard-subject-tag | issue:292155356 |
| 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/6/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d0ca1e275e5d163d872fbb3ff416742dbebbf60fe0b5a6ede2baa104413d03a8/utPLSQL/utPLSQL-SQLDeveloper/issues/6 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d0ca1e275e5d163d872fbb3ff416742dbebbf60fe0b5a6ede2baa104413d03a8/utPLSQL/utPLSQL-SQLDeveloper/issues/6 |
| og:image:alt | In version 0.1 all utPLSQL tests are executed as script in a SQL Developer worksheet and the test output is shown in the script output pane. This was easy to implement and is an acceptable solution... |
| 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