Add Coverage #43
Merged
Add Coverage #43
Conversation
This file contains 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
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.
Description
With the changes in this PR, one will be able to run testr with the
--coverageoption, and pytest will be run with coverage. At the end of the run, all coverage files are combined and a report is produced.Requires:
coverage.inifile in ska_testr (added coverage.ini ska_testr#52)Interface impacts
Added the
--coverageoption to run_testrTesting
Unit tests
Independent check of unit tests by [REVIEWER NAME]
Functional tests
I ran testr on the latest release but with newer
coverage, and produced this report