Title: Alternative hierarchical view · Issue #65 · utPLSQL/utPLSQL-SQLDeveloper · GitHub
Open Graph Title: Alternative hierarchical view · Issue #65 · utPLSQL/utPLSQL-SQLDeveloper
X Title: Alternative hierarchical view · Issue #65 · utPLSQL/utPLSQL-SQLDeveloper
Description: In version 1.0.0 test results are presented in a table. Here's an example: The table representation is good and allows to sort the result. For each column (test status, suitepath/description, runtime). This representation should be kept....
Open Graph Description: In version 1.0.0 test results are presented in a table. Here's an example: The table representation is good and allows to sort the result. For each column (test status, suitepath/description, runti...
X Description: In version 1.0.0 test results are presented in a table. Here's an example: The table representation is good and allows to sort the result. For each column (test status, suitepath/description, r...
Opengraph URL: https://github.com/utPLSQL/utPLSQL-SQLDeveloper/issues/65
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Alternative hierarchical view","articleBody":"In version 1.0.0 test results are presented in a table. Here's an example:\r\n\r\n\r\n\r\nThe table representation is good and allows to sort the result. For each column (test status, suitepath/description, runtime). This representation should be kept.\r\n\r\nHowever, an additional hierarchical representation would be optimal to vizualize the tree structure. Something like this:\r\n\r\n\r\n\r\nThe icon of a test could be replaced by the test status (success, failure, error, disabled) after completion. During execution the icon could be set to \"progress\". The same way as in the table representation. The runtime could be added at the end of the suitpath/description in square brackets, similar to the documentation reporter (e.g. `[0.042 s]`). \r\n\r\nIndicators for warning and info will not be included in the tree view. Sorting is also not possible. If this is wanted then switching back to the table representation is the way to go. \r\n\r\nThe tree should be fully expanded by default. \r\n\r\nSynchronization with detail tabs should work the same way as for the table representation.\r\n\r\nThe default view should be configurable in the utPLSQL preferences. Additionally switching view should be possible anytime within the utPLSQL realtime reporter, e.g. via context menu (kind of radio button logic).\r\n\r\nThe configuration to show suitepath or description should apply in the tree view as well.","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2019-07-13T08:14:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/65/utPLSQL-SQLDeveloper/issues/65"}
| 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:b2ce031f-38d6-46a3-fc5f-881d7107de8b |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 858C:1C445E:89E42B:BA535D:69692DFE |
| html-safe-nonce | 1867960bd10430d01b821f71b4781d1206bb10705babb728a18361d63e99850b |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4NThDOjFDNDQ1RTo4OUU0MkI6QkE1MzVEOjY5NjkyREZFIiwidmlzaXRvcl9pZCI6IjE1NzkyMDY3MzQzMDkzMDU4NTQiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 9f7f62f7841fd747ff746fbda9a66da83807415397ca7ac10d195b1090f14824 |
| hovercard-subject-tag | issue:467689643 |
| 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/65/issue_layout |
| twitter:image | https://opengraph.githubassets.com/a0bab07856d4911dd984afb3458931bec31f61d717b6d0d16df06beb41fe7946/utPLSQL/utPLSQL-SQLDeveloper/issues/65 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/a0bab07856d4911dd984afb3458931bec31f61d717b6d0d16df06beb41fe7946/utPLSQL/utPLSQL-SQLDeveloper/issues/65 |
| og:image:alt | In version 1.0.0 test results are presented in a table. Here's an example: The table representation is good and allows to sort the result. For each column (test status, suitepath/description, runti... |
| 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