Merged
Conversation
the source code needs the gradle sub-project to match what was analyzed
MikeNeilson
approved these changes
Apr 1, 2025
|
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.
Problem Description
SonarCloud is reporting an incorrect code coverage percentage because the jacoco code coverage was mismatched to the wrong gradle subproject.
Solution
Add in the integration testing coverage reports to the REST API subproject. Fix some minor sonar flagged issues while I'm looking at them.
how you tested the change
Tested from gradle CLI to verify coverage reports correctly.
Where the following done:
(Formerly called regression tests.)