Support for --logger parameter in dotnet test command

[madik7]

When running tests using dotnet test, the --logger parameter does not seem to generate the expected result file. The command:

dotnet test --no-restore --test-adapter-path:. --logger:"junit;LogFilePath=C:\path\{assembly}-test-result.xml;MethodFormat=Class;FailureBodyFormat=Verbose"

fails to produce the expected JUnit test result file.

Environment Details

• Test Logger: JunitXml.TestLogger 6.1.0

• XUnit.v3: 2.0.0

• .NET Version: net8.0

• Operating System: Windows 11

Steps to Reproduce

Install JunitXml.TestLogger version 6.1.0.

Run dotnet test with the --logger parameter as shown above.

Check if the result file is generated at the specified path.

Expected Behavior

The test result file should be generated successfully when specifying the --logger parameter.

Actual Behavior

No result file is created.

Additional Context

The official documentation (https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-with-dotnet-test) does not explicitly state that the --logger parameter is supported when using dotnet test.

Is support for --logger planned in future versions of dotnet test?

If not, what is the recommended approach to generating JUnit test results when using dotnet test?

Thank you!

[Youssef1313]

Are you running with Microsoft.Testing.Platform or VSTest? (i.e, do you have UseMicrosoftTestingPlatformRunner and TestingPlatformDotnetTestSupport?

[madik7]

I have in csproj:
<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport> <UseMicrosoftTestingPlatformRunner>true</UseMicrosoftTestingPlatformRunner>

[Youssef1313]

Yes, that means you are using Microsoft.Testing.Platform. This is explained in the doc page you linked: https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-with-dotnet-test#running-mtp-projects-with-vstest-mode

dotnet test is typically designed to run VSTest projects in VSTest mode, as that was its original purpose. However, to run MTP projects in dotnet test VSTest mode, you can use the Microsoft.Testing.Platform.MSBuild. From the user's perspective, this support is enabled by setting the TestingPlatformDotnetTestSupport MSBuild property to true (it is false by default for backward compatibility reasons). In simple terms, setting this property to true will cause Microsoft.Testing.Platform.MSBuild to change the VSTest target behavior, redirecting it to call InvokeTestingPlatform. This is an MSBuild target included in Microsoft.Testing.Platform.MSBuild, responsible for correctly running MTP test applications as executables. This means that VSTest-specific command-line options are silently ignored in this mode, such as --logger. This implies that there should be a way to pass MTP-specific command-line options, such as --report-trx, which is equivalent to using --logger trx in VSTest. Given the current limitations of the dotnet test CLI, the only way to include MTP-specific arguments is by appending them after an additional --. For instance, dotnet test -- --report-trx.

For your case, the package JunitXml.TestLogger needs to support Microsoft.Testing.Platform, which is currently work in progress. spekt/testlogger#172

[Youssef1313]

Note that JUnit reports are already supported in xUnit.v3 with --report-junit and --report-junit-filename.

[madik7]

Thank you for your response and help