Exclude source generated code from coverage results

[cam14754]

After running dotnet test with XPlat Code Coverage enabled, the resulting cobertura reports contains classes from auto generated files. I am running the tests on a .NET Maui project.

Specifically, I want to exclude all files ending in .g.cs.
Some examples of offending classes (names blurred):

<class name="~.~.Content.CircularProgressBar" filename="obj\Debug\net9.0-windows10.0.19041.0\~.~.Maui.Mvvm.SourceGenerators\~.~.Maui.Mvvm.SourceGenerators.BindablePropertyGenerator\CircularProgressBar_BindableProperty.g.cs" ...>

<class name="~.~.Content.ContentItemsCollectionView" filename="obj\Debug\net9.0-windows10.0.19041.0\~.~.Maui.Mvvm.SourceGenerators\~.~.Maui.Mvvm.SourceGenerators.BindablePropertyGenerator2\ContentItemsCollectionView_ContentLayout_BindableProperty.g.cs" `...>

I have attempted to remove these results by adding the following to the .runsettings file:

<ExcludeByFile>**/*.g.cs</ExcludeByFile>

<ExcludeByFile>
  **/bin/**/*,
  **/obj/**/*
</ExcludeByFile>

This does nothing to remove the above results due to our source code generators not including the proper attributes.

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

Currently there is someone working on adding the correct attributes to our source code generators, but for the moment I would like to see if a ExcludeByFile approach is possible. Strangely, the .NET Maui Community Toolkit source code generators get filtered no problem with the above, however our generators (which use Roslyn) does not get properly filtered.

Some questions I have:

• Are there known limitations with Roslyn hint-name generated paths that make a simple **/*.g.cs unreliable?
• Is there a recommended best-practice to exclude source-generated code purely via ExcludeByFile, or should I rely on attributes?

I feel this should be a simple clear cut problem, however nothing seems to filter these undesirable results.

Feel free to ask for any further clarification if needed, however the information I can give away is limited due to the closed source nature of the code.

[Bertk]

Please use ExcludeAssembliesWithoutSources option. The issue 14239 which has more information.

[cam14754]

Thanks for the response, I've tried with MissingAll and MissingAny. MissingAll gives the doesn't change anything, and MissingAny removes all packages from the results (I get no results). Is there any other ways to filter I could experiment with?

My current run settings:

<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
    <DataCollectionRunSettings>
        <DataCollectors>
            <DataCollector friendlyName="XPlat Code Coverage">
                <Configuration>
                    <Format>cobertura</Format>

                    <ExcludeByFile>**/*.g.cs</ExcludeByFile>

                    <ExcludeByAttribute>Obsolete,GeneratedCodeAttribute,CompilerGeneratedAttribute</ExcludeByAttribute>
                    <IncludeTestAssembly>false</IncludeTestAssembly>
                    <ExcludeAssembliesWithoutSources>MissingAll</ExcludeAssembliesWithoutSources>

                </Configuration>
            </DataCollector>
        </DataCollectors>
    </DataCollectionRunSettings>
</RunSettings>

[Bertk]

Thank you for the feedback. I did not use .runsettings configuration file and I recognized problems using it. The symptom is a code coverage file which has no details. I ask you kindly to use Default option (if you don't specify a runsettings file) and share you results.