.NET 9 preview1 (since 9.0.100-alpha.1.24073.1) is shipping with MSBuild TerminalLogger enabled by default for most dotnet workloads, including dotnet test. The experience is not perfect, so I am looking at ways to improve it, together with the terminal logger team.

The change for the vstest logger to integrate better with MSBuild was done here #2702 , it traces errors via msbuild output so it is visible in binary logger viewer etc.

This experience, paired with disabling other workarounds such as not reusing test nodes is enabled by default in net9 and can be opt-out by -p:VSTestUseMSBuildOutput=false build property or by MSBUILDENSURESTDOUTFORTASKPROCESSES=1 (after #4853). The change is implemented here: dotnet/sdk#38098

My wishlist:

Temporary output (appears when it happens and is rolled out when there is too much):

• getting passed tests as temporary output on the screen
• tests can be colorized (a "bug" doubles the time, most likely this is not accounting for the ansi codes to go missing once rendered? )
  

Static output:

• identification of the "task", so we can distinguish build success from test success
• success of test assembly, similar how it is reported for successfully built project
• single summary of test run with test counts
• summary of attachments