[BUG] No output recorded after unit testing using xUnit

[sharpchen]

Describe the Issue

No output recorded after unit testing.

Steps To Reproduce

1. I'm using xUnit.
2. example code

using Xunit;
using Xunit.Abstractions;

interface IAdapteeCannotImpl
{
    string DoWork();
}
sealed class Adaptee
{
    public string DoSpecialWork() =>
        $"Hello from {this.GetType().Name}!";
}
class Adapter : IAdapteeCannotImpl
{
    private readonly Adaptee _adaptee = new();
    public string DoWork() => _adaptee.DoSpecialWork();
}
static class ExistingImpl
{
    public static string DoWorkWith(IAdapteeCannotImpl obj) => obj?.DoWork()!;
}

public class AdapterTest
{
    private readonly ITestOutputHelper? _helper;
    public AdapterTest(ITestOutputHelper testOutputHelper) => _helper = testOutputHelper;

    [Fact]
    public void Test()
    {
        Adapter adapter = new();
        _helper!.WriteLine(ExistingImpl.DoWorkWith(adapter));
    }
}

3. Run the test, no output recorded.
   

Expected Behavior

This test works fine in Visual Studio.

Environment Information

• Windows 10
• Visual Studio Code 1.79.2
• Name: C# Dev Kit
  Id: ms-dotnettools.csdevkit
  Description: Official C# extension from Microsoft
  Version: 0.1.103
  Publisher: Microsoft
  VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit

[NebulousPsychology]

Seconded. my attempts to view output text from ITestOutputHelper have so far led me to three or four config-ways including .runsettings, and launch/task shenanigans. None are quite as basic as I'd hoped, and some are ignored or conflict with others. Simplest was a competing test explorer extension that allows direct access to the arguments of dotnet test.

[lucky51]

Is there any news about this?

[yedajiang44]

No progress or reply

[github-actions]

This issue has been marked as stale after 14 days of inactivity.@[@@], could you please take a look?

[NebulousPsychology]

I have observed that output is currently logged and viewable when a test fails, but I'm still interested in an option to force output that doesn't alter the expressed logic of the test

[ocallesp]

#989 should fix this issue

[peterwald]

Check the C# Dev Kit - Test Explorer output as xUnit may log it there.