first attempt at codecov#357
Draft
mabruzzo wants to merge 1 commit into
Draft
Conversation
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 is a first attempt at using CodeCov.
Right now, we are only looking at code-coverage from running the core-lib test-suite. We could also potentially get code-coverage from the unit-tests in the pygrackle suite (I suspect that getting C/C++/Fortran coverage from the answer-tests will slow things down quite a bit).
We can also collect pygrackle coverage (but haven't tried that yet).
I think we're ultimately going to want to use the "Component" functionality to differentiate between coverage of the core library and coverage of pygrackle. But that's something for the future