Title: Code Coverage : Unit Test and Coverage Schema different · Issue #174 · utPLSQL/utPLSQL-cli · GitHub
Open Graph Title: Code Coverage : Unit Test and Coverage Schema different · Issue #174 · utPLSQL/utPLSQL-cli
X Title: Code Coverage : Unit Test and Coverage Schema different · Issue #174 · utPLSQL/utPLSQL-cli
Description: Hello and greetings from Hannover, Germany. I have a question that affects the circumstance that our unit tests exists in a different schema than the tested code. The utPLSQL Framework invented the "a_coverage_schemes" - Parameter for th...
Open Graph Description: Hello and greetings from Hannover, Germany. I have a question that affects the circumstance that our unit tests exists in a different schema than the tested code. The utPLSQL Framework invented the...
X Description: Hello and greetings from Hannover, Germany. I have a question that affects the circumstance that our unit tests exists in a different schema than the tested code. The utPLSQL Framework invented the...
Opengraph URL: https://github.com/utPLSQL/utPLSQL-cli/issues/174
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Code Coverage : Unit Test and Coverage Schema different ","articleBody":"Hello and greetings from Hannover, Germany.\r\nI have a question that affects the circumstance that our unit tests exists in a different schema than the tested code. The utPLSQL Framework invented the \"a_coverage_schemes\" - Parameter for that case.\r\nFor example \r\nexec ut.run('UNITTEST', ut_coverage_html_reporter(), a_coverage_schemes=\u003eut_varchar2_list('ISUSER'));\r\nIs there a way to do the same call with utplsql-cli ?","author":{"url":"https://github.com/DrErique","@type":"Person","name":"DrErique"},"datePublished":"2020-02-10T11:42:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/174/utPLSQL-cli/issues/174"}
| 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:5a274b9a-94f9-5009-4066-cc4c13ac37e8 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | ECFE:26B0AA:2ABF12A:37D2AC7:696DBB28 |
| html-safe-nonce | 0078ef1dea89e7aec8c7502ee760d5b6b003a80fc1b81a9a4356760e725f55b1 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFQ0ZFOjI2QjBBQToyQUJGMTJBOjM3RDJBQzc6Njk2REJCMjgiLCJ2aXNpdG9yX2lkIjoiMjc2MjE3NjYwMzIxMzM4MDM5MiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 3d301747c172691629371f9458c4bc93955385b1d384412ce32813e0bc28e6ca |
| hovercard-subject-tag | issue:562506187 |
| 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/174/issue_layout |
| twitter:image | https://opengraph.githubassets.com/b9b92bff880414b6a91e3e2b005ecb25133e2bb503ce5ad0762c118887e7d7d1/utPLSQL/utPLSQL-cli/issues/174 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/b9b92bff880414b6a91e3e2b005ecb25133e2bb503ce5ad0762c118887e7d7d1/utPLSQL/utPLSQL-cli/issues/174 |
| og:image:alt | Hello and greetings from Hannover, Germany. I have a question that affects the circumstance that our unit tests exists in a different schema than the tested code. The utPLSQL Framework invented the... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | DrErique |
| hostname | github.com |
| expected-hostname | github.com |
| None | 4922b452d03cd8dbce479d866a11bc25b59ef6ee2da23aa9b0ddefa6bd4d0064 |
| 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 | 7e5ae23c70136152637ceee8d6faceb35596ec46 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width