Support for https://github.com/microsoft/codecoverage

[AdaskoTheBeAsT]

Hi,

do you plan support for https://github.com/microsoft/codecoverage

it should be external extension?

[devlead]

Hi,

Microsoft Code Coverage is NuGet/SDK tooling (Microsoft.CodeCoverage, dotnet-coverage, etc.), so Cake does not need to ship or wrap the collector itself. The main test scenario is already supported today via the DotNetTest alias and DotNetTestSettings.

Test projects (dotnet test --collect ...)

The Collectors property maps to --collect, so Microsoft's collector works out of the box:

DotNetTest("./tests/MyTests/MyTests.csproj", new DotNetTestSettings
{
    PathType = DotNetTestPathType.Project, // explicit --project (recommended for .NET 10+ / MTP)
    Configuration = "Release",
    Collectors = { "Code Coverage;Format=cobertura" },
    ResultsDirectory = "./artifacts/TestResults"
});

That produces the equivalent of:

dotnet test --project "./tests/MyTests/MyTests.csproj" --configuration Release --collect "Code Coverage;Format=cobertura" --results-directory "./artifacts/TestResults"

For .NET 10+ / Microsoft Testing Platform, use PathType = DotNetTestPathType.Project (or Auto) so Cake passes --project explicitly.

Ensure the test project references the Microsoft packages (e.g. Microsoft.NET.Test.Sdk and Microsoft.CodeCoverage). That part is project configuration, not Cake.

Other configuration options

Approach	Cake setting	Docs
Collector + format on CLI	Collectors	above
.runsettings file	Settings	DotNetTestSettings
Output location	ResultsDirectory	DotNetTestSettings
MSBuild properties (e.g. disable native instrumentation)	MSBuildSettings	DotNetTestSettings
Anything not yet modeled (e.g. --config-file for testconfig.json)	ArgumentCustomization	ToolSettings

Example with testconfig.json via WithArgumentCustomization:

var settings = new DotNetTestSettings
{
    PathType = DotNetTestPathType.Project,
    Collectors = { "Code Coverage;Format=cobertura" },
    ResultsDirectory = "./artifacts/TestResults"
}.WithArgumentCustomization(args =>
    args.AppendSwitchQuoted("--config-file", " ", "./testconfig.json"));

DotNetTest("./tests/MyTests/MyTests.csproj", settings);

Non-test apps (dotnet-coverage collect ...)

That path is separate from DotNetTest. Use DotNetTool or the Command alias for the dotnet-coverage global/local tool.

Should this be an external extension?

No extension is required for basic coverage collection. DotNetTest plus NuGet packages is sufficient.

An optional addin could make sense only for higher-level workflow (auto-discovering cobertura files under TestResults, chaining ReportGenerator, CI publish helpers), not for invoking --collect itself.

Hope that helps. Let us know if you hit a specific scenario that does not map cleanly to the settings above.