tests: attempt to gather code coverage info in the executable tests #638
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
It turns out that our tests of the built `tectonic` executable weren't gathering code coverage information about the code paths exercised in those tests. I *think* that it's not so hard to hack in some support to gather that information, so let's give it a try.
Codecov Report
@@ Coverage Diff @@
## master #638 +/- ##
==========================================
+ Coverage 46.25% 46.32% +0.07%
==========================================
Files 139 131 -8
Lines 60448 59079 -1369
==========================================
- Hits 27958 27367 -591
+ Misses 32490 31712 -778
Continue to review full report at Codecov.
|
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.
It turns out that our tests of the built
tectonicexecutable weren't gathering code coverage information about the code paths exercised in those tests. I think that it's not so hard to hack in some support to gather that information, so let's give it a try.CC @ralismark @Mrmaxmeier
xref: #636 assert-rs/assert_cmd#9