I made example and described issue in github repository:

https://github.com/MyLittleRobo/dub-coverage-test

On Monday, 21 March 2016 at 22:34:50 UTC, FreeSlave wrote:
> I made example and described issue in github repository:
>
> https://github.com/MyLittleRobo/dub-coverage-test

When doing -b unittest-cov dub only builds the current package in unittest-cov mode, all the dependencies are just build in their default mode.

It makes sense since you don't want to run their unittests, just your own.

On Tuesday, 22 March 2016 at 07:35:37 UTC, Sebastiaan Koppe wrote:
> On Monday, 21 March 2016 at 22:34:50 UTC, FreeSlave wrote:
>> I made example and described issue in github repository:
>>
>> https://github.com/MyLittleRobo/dub-coverage-test
>
> When doing -b unittest-cov dub only builds the current package in unittest-cov mode, all the dependencies are just build in their default mode.
>
> It makes sense since you don't want to run their unittests, just your own.

Then why does it show that unittest of dependency runs too? Every line is marked as executed once in the unittest of dependency.

On Tuesday, 22 March 2016 at 08:56:16 UTC, FreeSlave wrote:
> Then why does it show that unittest of dependency runs too? Every line is marked as executed once in the unittest of dependency.

You are right. Now I don't understand either...

Btw: I am using codecov.io and it does get the coverage correctly.

you just run `bash <(curl -s https://codecov.io/bash)` after a dub unittest-cov run and it will collect and upload.