Conversation
The coverage gate previously flagged any percentage drop > 0.05% as a regression. This caused false positives when well-covered code was extracted/moved out of a class — the percentage drops due to a ratio shift even though no test coverage was actually lost. Now a regression requires BOTH a percentage drop AND an increase in the absolute number of missed items. This correctly distinguishes real regressions (new uncovered code) from cosmetic ratio changes caused by refactoring. https://claude.ai/code/session_01XVBWUo2VM4B82ssZm1f2mu
Contributor
Test ReportTest Results
Code Coverage (Java 25)
|
When a class shows a coverage decrease, the PR report comment now includes a collapsible <details> section showing exactly which methods are uncovered or changed. The coverage gate failure message also includes method-level context. The JaCoCo XML parser is enhanced to extract per-method counters (name, descriptor, line/branch coverage) within each class. https://claude.ai/code/session_01XVBWUo2VM4B82ssZm1f2mu
andimarek
changed the title
When baseline method data is available, the method-level detail sections now only show methods whose coverage actually changed or that are new/ removed. Previously the hasMissed filter would show every partially-covered method, creating noise that buried the actual regressions. Falls back to showing all uncovered methods when no baseline method data exists yet. https://claude.ai/code/session_01XVBWUo2VM4B82ssZm1f2mu
The buildMethodDetails function now uses the same hybrid check as the coverage gate: percentage drop AND missed count increase. Previously it used a percentage-only check, which would show misleading detail sections for classes where code was merely extracted or moved. https://claude.ai/code/session_01XVBWUo2VM4B82ssZm1f2mu
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
2 participants
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.
Summary
<details>section listing exactly which methods are uncovered or changed, with line and branch coverage percentages and deltas vs baseline.parse-jacoco.jsnow extracts per-method counters (name, descriptor, line/branch/method coverage) from the JaCoCo XML. This data automatically flows into the baseline viamaster.ymlon the next merge, enabling method-level before/after comparisons.Files changed
.github/scripts/parse-jacoco.js.github/workflows/pull_request.yml.github/workflows/pr-report.ymlTest plan
https://claude.ai/code/session_01XVBWUo2VM4B82ssZm1f2mu