Title: Coverage files not mapped after upgrade to cli 3.1.7 · Issue #162 · utPLSQL/utPLSQL-cli · GitHub
Open Graph Title: Coverage files not mapped after upgrade to cli 3.1.7 · Issue #162 · utPLSQL/utPLSQL-cli
X Title: Coverage files not mapped after upgrade to cli 3.1.7 · Issue #162 · utPLSQL/utPLSQL-cli
Description: While trying new build pipeline with Azure on out uPLSQL-demo-project, I've decided to switch to latest utPLSQL-cli. It was then, when I've noticed that coverage is not getting reported on project files. At first I thought that it's rela...
Open Graph Description: While trying new build pipeline with Azure on out uPLSQL-demo-project, I've decided to switch to latest utPLSQL-cli. It was then, when I've noticed that coverage is not getting reported on project ...
X Description: While trying new build pipeline with Azure on out uPLSQL-demo-project, I've decided to switch to latest utPLSQL-cli. It was then, when I've noticed that coverage is not getting reported on ...
Opengraph URL: https://github.com/utPLSQL/utPLSQL-cli/issues/162
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Coverage files not mapped after upgrade to cli 3.1.7","articleBody":"While trying new build pipeline with Azure on out uPLSQL-demo-project, I've decided to switch to latest utPLSQL-cli.\r\nIt was then, when I've noticed that coverage is not getting reported on project files.\r\n\r\nAt first I thought that it's related to build configuration itself but after a bit of unsuccessful debugging I've decided to switch to utPLSQL-cli v3.1.6\r\n\r\nOn utPLSQL-cli v 3.1.6 coverage is generated without issues.\r\n\r\nThe reason for missing coverage is missing/invalid files mapping.\r\n\r\nSeems like regression in v3.1.7.\r\n\r\nWorth noting is that utPLSQL-core is using files-mapping to narrow the scope of coverage.\r\nWhen file names are passed in incorrect form, the result of mapping will be empty.\r\n\r\nI suspect that either:\r\n- the file mappings are getting passed in a different way (maybe swapped?)\r\n- one of regex_expression, type_mapping, owner/type/name/subexpression is not passed correctly\r\n\r\nThe difference in behavior can be seen here:\r\n- in [test run with 3.1.7](https://dev.azure.com/utplsql/utplsql/_build/results?buildId=51\u0026view=logs\u0026jobId=12f1170f-54f2-53f3-20dd-22fc7dff55f9\u0026taskId=23818292-9fa2-5b87-0a40-0d666b841585\u0026lineStart=129\u0026lineEnd=130\u0026colStart=1\u0026colEnd=1), coverage is empty and the sonar `test_results.xml` contains DB object_name as file_name.\r\n- in [test run with 3.1.6](https://dev.azure.com/utplsql/utplsql/_build/results?buildId=50\u0026view=logs\u0026jobId=12f1170f-54f2-53f3-20dd-22fc7dff55f9\u0026taskId=23818292-9fa2-5b87-0a40-0d666b841585\u0026lineStart=129\u0026lineEnd=130\u0026colStart=1\u0026colEnd=1) coverage is populated and the sonar `test_results.xml` contains expected file_names.","author":{"url":"https://github.com/jgebal","@type":"Person","name":"jgebal"},"datePublished":"2019-07-14T21:44:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/162/utPLSQL-cli/issues/162"}
| 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:d8298ba0-e41f-1751-6cbb-ac7e3879a3fa |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A72C:63FBA:535727:739D13:696E4554 |
| html-safe-nonce | c4fc0d62e9c35c0eeb97c388ac6e5328b9a82efe3657ccc1debbcf9eb2fe7d4e |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBNzJDOjYzRkJBOjUzNTcyNzo3MzlEMTM6Njk2RTQ1NTQiLCJ2aXNpdG9yX2lkIjoiODI3NTk5NzQzODE5MTIyNDE0OCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | e20119aef08321b11a14512f9c25f84d9878e826ce09d8661a14e300106194d5 |
| hovercard-subject-tag | issue:467888042 |
| 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-cli/162/issue_layout |
| twitter:image | https://opengraph.githubassets.com/920cfc7b1717e81968a4159fa8e1a21796987efd2c31baa945ac1f729faf9027/utPLSQL/utPLSQL-cli/issues/162 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/920cfc7b1717e81968a4159fa8e1a21796987efd2c31baa945ac1f729faf9027/utPLSQL/utPLSQL-cli/issues/162 |
| og:image:alt | While trying new build pipeline with Azure on out uPLSQL-demo-project, I've decided to switch to latest utPLSQL-cli. It was then, when I've noticed that coverage is not getting reported on project ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jgebal |
| hostname | github.com |
| expected-hostname | github.com |
| None | 3d96554e55b469c47dbcd31f74dc86278872b170531e84c6ce7f3389673e01d1 |
| turbo-cache-control | no-preview |
| go-import | github.com/utPLSQL/utPLSQL-cli git https://github.com/utPLSQL/utPLSQL-cli.git |
| octolytics-dimension-user_id | 15661281 |
| octolytics-dimension-user_login | utPLSQL |
| octolytics-dimension-repository_id | 88671831 |
| octolytics-dimension-repository_nwo | utPLSQL/utPLSQL-cli |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 88671831 |
| octolytics-dimension-repository_network_root_nwo | utPLSQL/utPLSQL-cli |
| 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 | ef576694863a4c791d0a5cc9d2b84384d4414bcd |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width