Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] coverageThreshold and mutationThreshold for report report-aggregate #1068

Closed
knysh opened this issue Aug 1, 2022 · 1 comment · Fixed by #1095
Closed

Comments

@knysh
Copy link

knysh commented Aug 1, 2022

Prerequisites:
I have a multi module maven project and I aggregate the report using report-aggregate.
mutationThreshold and coverageThreshold are different for all modules.
e.g.
mod0 coverage: 10%
mod1 coverage: 50%
mod2 coverage: 100%
general coverage: 53%

Steps:

  1. Common mutation report is okay and contains general percentages of coverage
  2. I would like to pass mutationThreshold and coverageThreshold

actual result: For now, I need to add threshold to each module to build project correctly
expected result: I would like to check only general coverage by passing thresholds to general or report-aggregate pom.xml

@Pfoerd
Copy link
Contributor

Pfoerd commented Sep 30, 2022

I have a similar issue. I'm currently over a PR to let ReportAggregator return a result object with aggregated coverage metrics and add thresholds for them in the pitest-maven aggregator mojo (vgl. Fork). Then one can configure thresholds in the parent pom.xml for the aggregated coverage metrics. I plan to raise the PR in the upcoming 2 weeks so stay tuned :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants