Skip to content

Aggregating coverage results doesn't work if the project has just one scoverage.xml file #144

Closed
@mthmulders

Description

@mthmulders

Not sure whether this is a bug or a feature... But I feel like it's a bug.

I have a SBT-project in the being, which currently has just one submodule. But it will have more the in the future, so that's why I figured multi-project setup would be appropriate.

Running sbt coverageAggregate gives the following output:

[info] Aggregating coverage from subprojects...
[info] Found 1 subproject report files [<project dir>/<submodule dir>/target/scala-2.11/scoverage-report/scoverage.xml]
[info] No subproject data to aggregate, skipping reports

It makes sense, since CoverageAggregator#aggregate explicitly checks to see if more than one file has been found.

I'd expect that aggregation of results also works if exactly one file would've been found.

If this is indeed a bug, let me know, I think I can contribute a simple PR for this 😃.

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