fix(test): enable coverage report via Sonar #533
Merged
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
paullatzelsperger
requested review from
florianrusch-zf,
wolf4ood and
stephanbcbauer
|
Kudos, SonarCloud Quality Gate passed!
|
wolf4ood
approved these changes
Jun 26, 2023
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.
WHAT
This is an attempt to enable Coverage Reports via SonarQube, by enabling the test coverage report generation.
WHY
No coverage reports where generated.
FURTHER NOTES
It is unclear which gradle tasks the Sonar server executes before running the analysis, so this is really more of an attempt.
Should this not be successful, we'll deactivate the automatic Sonar analysis, and replace it with an explicit
./gradlew sonar ...task, the way it was in the past.Closes #389