NUnit3TestAdapter v5 Does Not Display Console.WriteLine in Azure Pipelines

[nesreenmaged]

NUnit3TestAdapter v5 Does Not Display Console.WriteLine in Azure Pipelines
After upgrading from NUnit3TestAdapter v4 to v5, Console.WriteLine statements no longer appear in Azure DevOps Pipelines logs. This impacts both standard console output and Azure-specific logging

Code Example

[Test]
public void TestConsoleOutput()
{
    string version = "1.2.3";
    Console.WriteLine($"The version is {version}");
    Console.WriteLine($"##vso[task.setvariable variable=version;]{version}");
}

Environment:
NUnit3TestAdapter Version: 5.x
Test Framework: NUnit 3
Azure DevOps Pipeline: dotnet test
.NET Version: .NET8
OS: (windows-latest 2025)

This issue affects Azure DevOps logging commands (e.g., ##vso[task.setvariable]), making it difficult to pass test results dynamically to the pipeline.

[OsirisTerje]

@nesreenmaged I can't reproduce this.

Also note that a change in 4.6.0 was that ConsoleOut = 0 was fixed, so that it actually turns off console output. But the default is 1. Check if you inadvertently have that set to 0.
See https://docs.nunit.org/articles/vs-test-adapter/Tips-And-Tricks.html#consoleout

[nesreenmaged]

The console works locally, but it fails to run when executing the task in the Azure pipeline using the .NET Core test task.

[nesreenmaged]

The issue also persists in version 4.6.0. While the tests run correctly in a local environment, they fail to produce output in the Azure pipeline unless I explicitly add the following parameters:
--configuration $(BuildConfiguration) --filter FullyQualifiedName~MyTestName -- NUnit.ConsoleOut=2
(there is space before and after -- )

As a result, I need to update multiple pipeline tasks to include this workaround.
I believe the default behavior should include writing output to the console without requiring additional configuration.

[Evangelink]

It's possible this is linked to terminal logger functionality of .NET SDK. Could you try:

--configuration $(BuildConfiguration) /tl:off --filter FullyQualifiedName~MyTestName -- NUnit.ConsoleOut=2

Are you using Microsoft.Testing.Platform (MTP)?

[nesreenmaged]

Adding --NUnit.ConsoleOut=2 already resolved the issue, but since I have over 500 .NET Core test tasks in the Azure pipeline, the task requires significant refactoring. That's why I chose to downgrade to version 4.5.
The default setting should be enabled, as it was in previous versions.