Skip to content

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

@MichaelZinsmaier

Description

@MichaelZinsmaier

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions