dotnet test --verbosity doesn't list tests as they're run in 6.0 Preview 4

Install dotnet SDK 6.0.100-preview.2.21155.3.

Create a new NUnit or xUnit test project with dotnet new nunit / dotnet new xunit.

Run dotnet test -v d (aka --verbosity detailed)

You get the following output:

SDK 6.0.100-preview.2.21155.3

NUnit

       Task "Microsoft.TestPlatform.Build.Tasks.VSTestTask"
Microsoft (R) Test Execution Command Line Tool Version 16.9.0-preview-20210125-03
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.

Passed!  - Failed:     0, Passed:     1, Skipped:     0, Total:     1, Duration: 19 ms - NunitTests.dll (net5.0)
       Done executing task "Microsoft.TestPlatform.Build.Tasks.VSTestTask".

xUnit

       Task "Microsoft.TestPlatform.Build.Tasks.VSTestTask"
Microsoft (R) Test Execution Command Line Tool Version 16.9.0-preview-20210125-03
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.

Passed!  - Failed:     0, Passed:     1, Skipped:     0, Total:     1, Duration: 1 ms - XunitTests.dll (net5.0)
       Done executing task "Microsoft.TestPlatform.Build.Tasks.VSTestTask".

Note that there is no output about the tests that are being run, in particular test names being printed as they’re run.

Now change the <TargetFramework> of the projects to net5.0 and create a global.json (dotnet new globaljson --sdk-version=5.0.103) containing:

{
  "sdk": {
    "version": "5.0.103"
  }
}

Run dotnet test -v d again. You get more verbose output:

SDK 5.0.103

NUnit

       Task "Microsoft.TestPlatform.Build.Tasks.VSTestTask"
Microsoft (R) Test Execution Command Line Tool Version 16.8.3
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
NUnit Adapter 3.17.0.0: Test execution started
Running all tests in C:\Code\Projects\DotnetTest\NunitTests\bin\Debug\net5.0\NunitTests.dll
   NUnit3TestExecutor discovered 1 of 1 NUnit test cases
NUnit Adapter 3.17.0.0: Test execution complete
  Passed Test1 [18 ms]

Test Run Successful.
Total tests: 1
     Passed: 1
 Total time: 0.7272 Seconds
       Done executing task "Microsoft.TestPlatform.Build.Tasks.VSTestTask".

xUnit

       Task "Microsoft.TestPlatform.Build.Tasks.VSTestTask"
Microsoft (R) Test Execution Command Line Tool Version 16.8.3
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v2.4.3+1b45f5407b (64-bit .NET 5.0.3)
[xUnit.net 00:00:00.31]   Discovering: XunitTests
[xUnit.net 00:00:00.33]   Discovered:  XunitTests
[xUnit.net 00:00:00.34]   Starting:    XunitTests
[xUnit.net 00:00:00.39]   Finished:    XunitTests
  Passed XunitTests.UnitTest1.Test1 [1 ms]

Test Run Successful.
Total tests: 1
     Passed: 1
 Total time: 0.9189 Seconds
       Done executing task "Microsoft.TestPlatform.Build.Tasks.VSTestTask".

[adamralph]

FWIW, you can work around the problem like so:

dotnet test --logger "console;verbosity=normal"

[adamralph]

I guess the answer is no, since 6.0.100 (RTM) still has the problem.