Using ReSharper, how to show debug output during a long-running unit test?

问题

I'm using xUnit with the ReSharper test runner and the xUnitContrib resharper plugin.

When I have a long-running test, I'd like to be able to output some progress indicator to the Unit Test Output window.

I've tried Debug.WriteLines, Trace.WriteLine and Console.WriteLine. All of which have the same behavior - nothing shows in the output window until the test has completed.

For example:

[Fact]
public void Test()
{
    Debug.WriteLine("A");
    Trace.WriteLine("B");
    Console.WriteLine("C");

    Thread.Sleep(10000);
}

The test shows no output until the 10 seconds have elapsed and the test completes. How do I get output along the way?

UPDATE 1

I tried also with MSTest and NUnit. NUnit is the only one that shows output along the way.

MSTest and XUnit don't return any output until the test completes. The weird part is that while the XUnit and NUnit test output looks like this:

A
B
C

The MSTest output looks like this:

C


Debug Trace:

A
B

Given all of these variations, I think the answer is that it is up to the test runner implementation to decide how and when to output. Does anyone know if it is possible to configure the XUnit test runner?

UPDATE 2

I think this must be a deficiency in xUnitContrib. Posted to their CodePlex issue tracker.

回答1:

If you used xUnit.net 1.x, you may have previously been writing output to Console, Debug, or Trace. When xUnit.net v2 shipped with parallelization turned on by default, this output capture mechanism was no longer appropriate; it is impossible to know which of the many tests that could be running in parallel were responsible for writing to those shared resources. Users who are porting code from v1.x to v2.x should use one of the two new methods instead.

Have a look here for example of how to perform logging with xUnit.net v2:

http://xunit.github.io/docs/capturing-output.html

This is the example:

using Xunit;
using Xunit.Abstractions;

public class MyTestClass
{
    private readonly ITestOutputHelper output;

    public MyTestClass(ITestOutputHelper output)
    {
        this.output = output;
    }

    [Fact]
    public void MyTest()
    {
        var temp = "my class!";
        output.WriteLine("This is output from {0}", temp);
    }
}

回答2:

Per Brad Wilson:

This is a limitation in xUnit.net, not the Resharper adapter.

We will be addressing this in v2 of xUnit.net.

http://xunitcontrib.codeplex.com/workitem/4160

回答3:

ReSharper somehow removed the default listener in unit tests. To display text in the Output window, just add this line:

Debug.Listeners.Add(new DefaultTraceListener());

回答4:

For NUnit this works:

Console.SetOut(TestContext.Progress);

** The late answer is because I had the same problem, and I just solved it. may help others

回答5:

XunitLogger uses AsyncLocal<T> to keep track of the logging context so calls to Trace.Writeline and Console.Writeline can be routed to the correct instance of ITestOutputHelper.

Usage:

static class ClassBeingTested
{
    public static void Method()
    {
        Trace.WriteLine("From Trace");
        Console.WriteLine("From Console");
        Console.Error.WriteLine("From Console Error");
    }
}

public class TestBaseSample  :
    XunitLoggingBase
{
    [Fact]
    public void Write_lines()
    {
        WriteLine("From Test");
        ClassBeingTested.Method();

        var logs = XunitLogger.Logs;

        Assert.Contains("From Test", logs);
        Assert.Contains("From Trace", logs);
        Assert.Contains("From Console", logs);
        Assert.Contains("From Console Error", logs);
    }

    public TestBaseSample(ITestOutputHelper output) :
        base(output)
    {
    }
}

回答6:

The easiest I've found is to utilize log4net and create a console logger. Along the way, as you're running, you'd call logger.Info("info here"); or log.Debug("info here"); - really whatever your preferred logging level - and the output will show in Resharper Unit Test Sessions.

Read more about the log4net framework on the Apache log4net homepage. The configuration examples will also be invaluable.