Consider setting Console.OutputEncoding for dotnet test and friends

[bradwilson]

There was a change in Windows Terminal 1.17 that causes .NET applications that output Unicode characters to the console to have them garbled, because of the default output encoding. This does not happen in prior versions of Windows Terminal, nor in classic "conhost.exe" console windows.

xUnit.net uses characters which are corrupted now when run on Windows Terminal through dotnet test and friends.

Output from xunit.console.exe:

Output from dotnet test (in Windows Terminal-hosted Powershell):

Output from dotnet test (in conhost-hosted Powershell):

While strictly speaking this isn't a bug in VSTest (or xUnit.net), we opted fixed this in xunit/xunit@c4b6ed0 on our side. I would recommend that you consider doing this as well, so that any output from testing frameworks which is outside of ASCII can be presented properly in Windows Terminal.

AB#1865057

[nohwnd]

Thanks for the tip!

[nohwnd]

We will need to check with someone using some exotic system (like chinese) to see if everything looks okay and then implement this.