Report test coverage on builds and pull requests - #21
Merged
Conversation
The build already collected Cobertura coverage but only uploaded the raw XML. ReportGenerator now produces a per-assembly markdown summary, posted as a sticky PR comment and written to the job summary on every run. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Summary
|
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.
Changes
The build has always collected Cobertura coverage (
coverage.runsettings, scoped toPostie.*minus tests and samples) but only uploaded the raw XML as an artifact. This adds the reporting layer, following the same approach as the ASM repo:Postie's single test invocation means no separate coverage job or artifact merge is needed (unlike ASM's 16-project matrix) — three steps in the existing
buildjob. The job gainspull-requests: writefor the comment; both new actions are pinned by commit SHA per this repo's convention.Known limitation (same as ASM): fork PRs get a read-only token, so the comment step can't post there — the job summary still covers it.
This PR should demonstrate the feature on itself.
🤖 Generated with Claude Code