Consider: Disable MTP's own TerminalTestReporter when running under server mode (pipe specifically maybe?)

[Youssef1313]

When running with dotnet test using the pipe protocol, SDK's TerminalTestReporter is responsible for reporting the test results, progress, etc...

Doing that work in the test app itself might lead to:

1. Work being thrown away.
2. Unnecessary console writes.
3. Duplicate information printed by TerminalTestReporter when we attempt to print the test app process standard output/err.

This is also quite related to dotnet/sdk#51615.

[Evangelink]

If I recall correctly this is the behavior in place for the server mode (VS)

[nohwnd]

https://github.com/microsoft/testfx/blob/main/src/Platform/Microsoft.Testing.Platform/OutputDevice/TerminalOutputDevice.cs#L348

It prints at least here, if all of that info is forwarded via server then there should be no point for activating terminal reporter. Output of the child process should still be collected though, because binaries can write to the native stream so C# won't see it and won't forward it (e.g. TAEF does that).

[Youssef1313]

If I recall correctly this is the behavior in place for the server mode (VS)

@Evangelink I see nowhere we do this.

[Evangelink]

I got confused by this part of the code: https://github.com/microsoft/testfx/blob/main/src/Platform/Microsoft.Testing.Platform/OutputDevice/OutputDeviceManager.cs#L37-L43

I thought that in server mode we were only using a different output not just writing to both.