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

Multimodule aggregation for individual reports / bug in full aggregation? #119

Open
MichaelZinsmaier opened this issue Oct 16, 2019 · 0 comments

Comments

@MichaelZinsmaier
Copy link

Hi all,

I just upgraded from a very old version to the current 3.2.0. Unfortunately the aggregate task works only on the new "all"Report.

problem I) this is a change that screws up our historical comparison (although its arguably better)
problem II) I think it is buggy, compared to the old values the number of statements increases and the coverage decreases. My guess would be that the aggregator sums up the statements per testReport. At least in a few cases the number of statements doubled exactly (not everywhere though).

for now I switched back to the old behavior (just aggregating everything under test), the following snippet does the trick

task aggregateOnlyTestScoverage(type: org.scoverage.ScoverageAggregate) {
    coverageDebug.set(false)
    coverageOutputCobertura.set(false)
    coverageOutputHTML.set(true)
    coverageOutputXML.set(true)
    deleteReportsOnAggregation.set(false)
    reportDir.set(file("$buildDir/scoverage/"))

    def reportDirs = project.subprojects.collect {Project p -> file(p.buildDir.toPath().toString() + "\\reports\\ScoverageTest")}
    dirsToAggregateFrom.set(reportDirs)

    runner = new org.scoverage.ScoverageRunner(project.configurations.scoverage)
}

best Michael

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

No branches or pull requests

1 participant