Add COVERAGE_RUN_ID to utPLSQL context #1194
Merged
Conversation
…ate coverage reporting when runnign tests against the coverage module of the framework.
Contributor
Codecov Report
@@ Coverage Diff @@
## develop #1194 +/- ##
===========================================
+ Coverage 94.77% 94.79% +0.02%
===========================================
Files 104 104
Lines 4879 4881 +2
Branches 22 22
===========================================
+ Hits 4624 4627 +3
Misses 247 247
+ Partials 8 7 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
Kudos, SonarCloud Quality Gate passed! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This will allow for more accurate coverage reporting when running tests against the coverage module of the framework.
With this, in the test, we can get the current
coverage_run_idand pass it to the JOB that runs utPLSQL in separate session.After the JOB is finished, we can then copy the output from
ut3_developcoverage tables intout3coverage tables.That way, we will get a full picture of the coverage gathered in the course of utPLSQL test-run with coverage enabled.
Most of the setup is already in place in our tests. The only missing peace was the ability to tie the current
ut3test-run with the coverage gathered by jobs.So now, after each test JOB, we can copy the coverage over to
ut3.I suggest using negative-id's when performing the copy from
ut3_developprofiler/dbms_plsql_cov tables.That way we can:
run_id