This repository was archived by the owner on Jan 30, 2023. It is now read-only.
Aggregate measures for custom coverage metrics. #447
Merged
Conversation
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
|
Here's an example of those custom measures showing up in the activity graph.
|
|
And here's those measures showing up in the measures section. (those should be all under tests, so I'll fix that.)
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Measures for custom metrics reported on files are no longer aggregated automatically, so this PR intends to fix that by implementing a custom
MeasureComputer. It gets executed by SonarQube's compute engine and allows us to aggregate measures for all the children across all of the project's components i.e. directories and modules.I've not tested this yet and
ScoverageMeasuresis missing unit tests.Should fix #432 when finished.