Async methods excluded from coverage after updating to 2.8.1

[Malivil]

Using coverage format "OpenCover" and the coverlet.msbuild package
In version 2.8.0 an async method in my Web API class shows no coverage (because I haven't written tests yet):

In version 2.8.1, the same method is just excluded from coverage entirely:

The coverage.opencover.xml shows a complete missing section for the method:

I do not have a minimal reproduction example but if needed I can probably make one.
May be related to 528956b

[MarcoRossignoli]

Do you have ExcludeFromCodeCoverage attribute somewhere?
Do you see missing coverage only for this method in source or for all method of same class?

I do not have a minimal reproduction example but if needed I can probably make one.

Would be great!It's hard without repro.

cc: @matteoerigozzi

[Malivil]

This class does not have ExcludeFromCodeCoverage
Only the two methods marked async are not showing coverage.

I will try to make a simple reproduction project. I'll comment here with the repo when it's complete.

[MarcoRossignoli]

Ok thanks a lot!

[Malivil]

Here's a repro with the minimum example: https://github.com/Malivil/CoverletAsyncRepro
If you run the .bat file within the .Tests project it will generate a report in the TestResults folder

Changing the version of the coverlet.msbuild in the .Tests csproj to 2.8.0 and then re-running the .bat will show the function as uncovered as it should.

[MarcoRossignoli]

Great, stay on 2.8.0 for now I'll come back asap.

[bgoymer-unilink]

Hi there,

I've also noticed this issue recently, it appears to be something to do with the /p:ExcludeByAttribute=CompilerGeneratedAttribute argument, as removing this will cause the coverage to be successfully reported. Thanks for the tip of going back to 2.8.0 as that also solves the issue for now.

[MarcoRossignoli]

@Malivil can you confirm that removing /p:ExcludeByAttribute=CompilerGeneratedAttribute solve(disappear, but it's clearly a bug) issue?

[bgoymer-unilink]

@MarcoRossignoli I feel that I need to clarify; athough removing the argument appears to solve this issue, it will cause all our auto-implemented properties in our DTOs to record no coverage without being explictly tested, which we did not have to do prior to 2.8.1.

[MarcoRossignoli]

@bengoymer yes I mean this is a bug but if we know that is related to that parameter we can fix more fast.

[bgoymer-unilink]

@MarcoRossignoli perfect, thank you.

[MarcoRossignoli]

@bengoymer can you try to remove that param and filter out DTO using source file filtering(if DTO are in separate files)?
https://github.com/tonerdo/coverlet/blob/master/Documentation/MSBuildIntegration.md#source-files

[bgoymer-unilink]

@MarcoRossignoli yes, just done that. If I filter out the DTOs using the source file filtering, and remove ExcludeByAttribute the coverage of the async functions is as I'd expect.

[Malivil]

@MarcoRossignoli Removing that exclude does fix this issue. The reason I had that was mostly to exclude generated property Getters and Setters.

[MarcoRossignoli]

@Malivil sorry I wasn't clear, this is only to confirm that the issue disappear if you remove that attribute for those async method, it won't fix the issue it's to have a double confirmation on where issue could be.

[Malivil]

@MarcoRossignoli I understand. I was just adding clarity as to why I had it there in the first place =)

I guess I should have used a different word than "fix"

[MarcoRossignoli]

So if you remove that attribute you see async methods uncovered yet?

[Malivil]

Yes, removing the attribute exclude shows the async methods as being uncovered, that's what I meant when I said it "[fixed] the issue". Sorry for not being clear =)

[viceice]

Seeing this too, workaround:

<!-- <ExcludeByAttribute>Obsolete,GeneratedCodeAttribute,CompilerGeneratedAttribute</ExcludeByAttribute> -->
<ExcludeByAttribute>Obsolete</ExcludeByAttribute>

[MarcoRossignoli]

@Malivil can you try the workaround(temporary) and tell me if it works?

[Malivil]

Where does that go? In the test .csproj?

[viceice]

@Malivil It depends on your usage. We use the collector, so we add this to the runsettings file.

[Malivil]

We use the msbuild integration as shown in the test repo: https://github.com/Malivil/CoverletAsyncRepro

[viceice]

You need to add it to your test csproj.

https://github.com/tonerdo/coverlet/blob/master/Documentation/MSBuildIntegration.md

[Malivil]

That's what I thought.

@MarcoRossignoli: This workaround behaves the same as the command-line change which I think is expected.

[MarcoRossignoli]

This workaround behaves the same as the command-line change which I think is expected.

Not clear what you mean, /p:ExcludeByAttribute=Obsolete for msbuild

[Malivil]

This workaround behaves the same as the command-line change which I think is expected.

Not clear what you mean, /p:ExcludeByAttribute=Obsolete for msbuild

Using that switch behaves the same as if I don't use ExcludeByAttribute at all. I don't have anything annotated with Obsolete so it has no affect.

[MarcoRossignoli]

Using that switch behaves the same as if I don't use ExcludeByAttribute at all. I don't have anything annotated with Obsolete so it has no affect.

Yes the test was only to understand if we're excluding something generated by compiler and also with Obsolete and maybe the result could be a bit different. But ok thanks for help on investigation.

[Malivil]

If I use Obsolete, GeneratedCodeAttribute, or a combination of both it does not exclude the async method. If I add CompilerGeneratedAttribute back in to either the switch or the test .csproj then it does exclude the async method again. So it seems to be narrowed to CompilerGeneratedAttribute specifically.

[MarcoRossignoli]

So it seems to be narrowed to CompilerGeneratedAttribute specifically.

Yep, my hope was find a temporary workaround with no version downgrade, but seem not possible at the moment.

[MarcoRossignoli]

@Malivil we did some check, actually the behaviour is correct, we fixed a bug where CompilerGeneratedAttribute wasn't honored, so now correct behaviour is to exclude class with that attribute and in your case every async state machine(autogenerated class by roslyn compiler for async methods) has got that attribute.
You cannot use that filter to remove autoprops from instrumentation anymore and it's correct.
A solution for now is to use ExcludeByFile filter and remove al DTOs source files.

We should add support for skip autoprops #328

[Malivil]

I cannot exclude the every file that has properties in it. Looks like I'll need to remove that exclude and have my coverage drop until #328 is complete

[MarcoRossignoli]

Understood, for now feel free to close this issue, I'll move that issue up in queue.