How to get MSBuild binary logs from MTP with dotnet test?

[martincostello]

I have a custom MSBuild target that I call ReportGenerator with, which is defined with AfterTargets="InvokeTestingPlatform", but it isn't firing.

I tried to debug this with an MSBuild binary log, but the log doesn't appear to contain any trace of the InvokeTestingPlatform target.

I ran dotnet test -bl, which generates msbuild.binlog and msbuild-dotnet-test.binlog, but neither find the InvokeTestingPlatform target in it, but I know it's running as I can see the effects of another target I have that is defined with BeforeTargets="_MTPAddArguments;InvokeTestingPlatform".

I can see the MTP build in msbuild.binlog:

But msbuild-dotnet-test.binlog doesn't appear to contain anything other than evaluation:

[Youssef1313]

If you are talking about the MTP-based dotnet test that is shipping in .NET 10, we don't invoke any MSBuild targets for running tests. The whole logic is embedded in the dotnet(.exe) process where we start the test app as child processes. Collecting coverage via MSBuild is unfortunately not supported.

[martincostello]

I'm confused - I use MSBuild targets to customise the arguments to MTP before it's invoked...

I just made a change to them to double check:

[Youssef1313]

_MTPAddArguments is run (we do it programmatically here), but not InvokeTestingPlatform. The actual test execution doesn't happen via any targets.

[martincostello]

Ah, that explains why I just need to make this change to add _MTPAddArguments: martincostello/build-kit@0f225e0

So basically my whole MSBuild customization setup is junked by MTP v2?

[martincostello]

Collecting coverage via MSBuild is unfortunately not supported.

For clarity, I'm not collecting coverage - I'm running ReportGenerator to post-process the output from the tests to generate human-readable reports.

[Youssef1313]

fwiw, for adjusting TestingPlatformCommandLineArguments, it's better to not rely on _MTPAddArguments and use ComputeRunArguments instead.

For ReportGenerator, we need to discuss internally how to best move forward here. The initial plan was to not have any MSBuild hooks here for dotnet test. FYI @nohwnd @baronfel @mariam-abdulla