Peter Liljenberg

@iSuper-Ray Sorry, it's not possible to run against an already executing process, since coverlet works by instrumenting the binaries before they are run.

The coverlet VSTest collector driver is configured with a runsettings file, you can find the documentation for that here: https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md The first link you provided is about coverlet, which as...

@tapika Have you specified the runsetting files for coverlet on the command line? There's an example at https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md#coverlet-options-supported-by-vstest-integration : dotnet test --collect:"XPlat Code Coverage" --settings coverlet.runsettings The Visual Studio code...

It sounds like a good way to solve generated files once and for all. But are non-generated source files embedded in the PDB too? If they are, it would break...

Hi @danpowell88, coverlet relies on finding the source code files to determine what modules to instrument. Without the source code in the exact same path on the machine running the...

I've been curious about getting per-test coverage reports since the file formats tend to support it, but it would require a fair bit of redesign of the hit collection and...

> If it's not possible to figure out which tests ran through a specific line, could it perhaps be possible to generate a coverage file per test in the test...

I don't know much about the collector architecture, but it's a good point to investigate that. May not need any of the call stack analysis or hit array per test,...

A more consistent parameter name may be `ExcludeAssembliesWithoutSources`. (Edit: the description above have been updated to this name now, replacing the original idea `IgnoreAssembliesWithoutSources`.)

I think you must specify the runsettings file on the command line, there's no file that is picked up by default. Try adding `--settings coverlet.runsettings`, adapting the file name to...