coverage of entire project

[fommil]

It looks like the coverage report for a module is only gathered for tests run in that module.

I'd like to be able to see the coverage of my entire (multi module) project when I run some integration tests... to see what I can delete 😄 ... is that possible?

[sksamuel]

The sbt coverageAggregate functionality is meant to cover that.

[fommil]

Hmm, it not sure it does that. I'm seeing 0% coverage outside my top level module

[fommil]

yeah, coverageAggregate definitely doesn't do what I'm asking. It seems to just join reports together. If I have a project with modules A and B, B depends on A, A doesn't have any tests, B has tests that exercise the entire codebase (including everything in A), then a coverageAggregate will show 0% coverage for module A.

[sksamuel]

So your tests for A are actually part of B. Then yeah that wouldn't work.
That's like you writing unit tests for scala.collection and wanting code
coverage for that.

On 29 June 2015 at 17:42, Sam Halliday notifications@github.com wrote:

yeah, coverageAggregate definitely doesn't do what I'm asking. It seems
to just join reports together. If I have a project with modules A and B, B
depends on A, A doesn't have any tests, B has tests that exercise the
entire codebase (including everything in A), then a coverageAggregate
will show 0% coverage for module A.

—
Reply to this email directly or view it on GitHub
#112 (comment)
.

[fommil]

Yeah, kind of. The point is that I have integration tests (which live in B) and I want to see what parts of the code are dead across the project.

[sksamuel]

I guess it could be done. Worst case is you could do

sbt compile
sbt test

as two separate things that would result in the profile data. Then

sbt report (or something)

to clean up after.

On 29 June 2015 at 18:02, Sam Halliday notifications@github.com wrote:

Yeah, kind of. The point is that I have integration tests (which live in
B) and I want to see what parts of the code are dead across the project.

—
Reply to this email directly or view it on GitHub
#112 (comment)
.

[RichardBradley]

Does this workaround fix your case?
#87 (comment)

When run on the example project quoted there, tests in the "core" project add to coverage measured on the "utils" project.

[RichardBradley]

I'm using ver 1.3.1 to produce coverage reports where some of the tests in project A cover classes in project B and it's working well for me.