Repository navigation
ci: publish test results and track test coverage over time - #573
Merged
Merged
Conversation
Publish JUnit results from both test stages and record JaCoCo coverage with the Jenkins Coverage plugin, in post always blocks so failing tests still land in the trends. Coverage is informational: a reporting problem marks the build unstable instead of failing it and blocking the release. Gradle gets the built-in jacoco plugin with an XML report. The IntelliJ test framework loads classes through its own class loaders, so the test task sets includeNoLocationClasses (and excludes jdk.internal), and the generated lexer/parser/PSI code is left out of the report. Locally this measures about 94% line and 77% branch coverage. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
sjrx-claude-sandbox
force-pushed
the
ci/test-coverage
branch
from
October 27, 2026 22:43
5f11145 to
dc3ef8b
Compare
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
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.
Publish JUnit results from both test stages and record JaCoCo coverage with the Jenkins Coverage plugin, in post always blocks so failing tests still land in the trends. Coverage is informational: a reporting problem marks the build unstable instead of failing it and blocking the release.
Gradle gets the built-in jacoco plugin with an XML report. The IntelliJ test framework loads classes through its own class loaders, so the test task sets includeNoLocationClasses (and excludes jdk.internal), and the generated lexer/parser/PSI code is left out of the report. Locally this measures about 94% line and 77% branch coverage.