GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Standalone coverage by jgebal · Pull Request #1079 · utPLSQL/utPLSQL

Conversation

@jgebal

@jgebal jgebal commented Jun 13, 2020 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

Resolves #1025

Coverage can now be gathered outside of utPLSQL test run (without invoking ut.run)

Example:

begin 
    ut_runner.coverage_start('A6AA5B7361251CE6E053020011ACA078');
    some_schema.some_package.procedure; 
    ut_runner.coverage_stop();
end;
/

In same session or even a separate session (once previous call was finished) run:

    select *
      from
        table (
          ut_coverage_cobertura_reporter( ).get_report(
            ut_coverage_options(
              coverage_run_id => 'A6AA5B7361251CE6E053020011ACA078',
              include_objects => ut_varchar2_rows('SOME_PACKAGE'),
              schema_names => ut_varchar2_rows('SOME_SCHEMA')
              )
            )
          );

TODO

  • Documentation
  • Internal code cleanup and refactoring
  • Test fixes

@ksawerykarwacki - feel free to give a try to the version from this feature branch.
Let me know if you encounter any issues or have any questions.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
jgebal added 5 commits June 11, 2020 00:23
@jgebal
Reworked coverage to allow for gathering coverage without calling utP…
93fd222
…LSQL.

Enables multi-session coverage too.
@jgebal
Removed mocking API for coverage,
641d87c
Fixed failing tests for 11.2 and 12.1
Refactored some parts of tests
@jgebal
Workaround for 12.2 issue with conditional compilation in package spec.
52e1db9
Added missing testcase for get_report_cursor
@jgebal
cleanup of unneeded safety code
a17c3af
@jgebal
Refactoring tests
09ab226
@jgebal jgebal mentioned this pull request Jun 21, 2020
Use coverage without ut.run() #1025
Closed
jgebal added 2 commits June 21, 2020 14:18
@jgebal
Reorganized and cleaned up tests to have only one package used for co…
e9e4b9e
…verage tests.
@jgebal
Removed dead code.
a4ae4cf
@jgebal

jgebal commented Jun 21, 2020 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member Author
  • client_character_set needs to be added to get_report and get_report_cursor.
    Currently it is missing.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

jgebal added 2 commits June 21, 2020 20:59
@jgebal
Added support for client_character_set as report parameter.
0e72abc
@jgebal
Made coverage_run_id mandatory in ut_coverage_options
955de5c
Added documentation
@jgebal
jgebal requested review from PhilippSalvisberg, lwasylow and pesse June 21, 2020 21:36
@jgebal jgebal added this to the 3.1.11 milestone Jun 21, 2020
@jgebal jgebal added the enhancement label Jun 21, 2020
@sonarqubecloud

sonarqubecloud Bot commented Jun 21, 2020

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

82.3% 82.3% Coverage
0.9% 0.9% Duplication

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@jgebal

jgebal commented Jun 28, 2020

Copy link
Copy Markdown
Member Author

@pesse , @PhilippSalvisberg, @lwasylow
Any comments on the way the new API is built?

Can one of you review the documentation and provide some feedback before I merge?

I think it's a major addition to current API and would like to know that I got it right.

Also, it would be great to know that the documentation is sufficient.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@jgebal

jgebal commented Jul 18, 2020

Copy link
Copy Markdown
Member Author

Merging as there are no review comments in 20 days.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@jgebal
jgebal merged commit ad39737 into develop Jul 18, 2020
@jgebal
jgebal deleted the feature/standalone_coverage branch July 18, 2020 16:52
@PhilippSalvisberg PhilippSalvisberg mentioned this pull request Feb 22, 2021
Deviation between dbms_utplsql_code_coverage and html_reporter #1124
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@lwasylow lwasylow Awaiting requested review from lwasylow
@pesse pesse Awaiting requested review from pesse
@PhilippSalvisberg PhilippSalvisberg Awaiting requested review from PhilippSalvisberg

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

enhancement

Projects

None yet

Milestone

v3.1.11

Development

Successfully merging this pull request may close these issues.

Use coverage without ut.run()

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@jgebal
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.