3

Resolved

xUnit traps/buffers output from tests until the test is complete

description

When using NUnit, we're used to being able to see the progress of our long-running integration tests in the output from the build server (the tests write some progress output).

xUnit appears to trap output from the tests, and doesn't write any of it to the console until the entire test is complete. This behavior also occurs in the gui test runner.

It would be very useful to have the ability for xUnit to flush output from tests as it received it, instead of just when the test is completed.

comments

BradWilson wrote Mar 19, 2011 at 10:55 PM

This isn't doable without major architectural changes, so it's likely that we'll close this a "Won't Fix".

BradWilson wrote Mar 30, 2013 at 8:32 PM

We have decided to stop all capture of output in v2, so you will get NUnit's default behavior now with xUnit.net v2.

pixelshaded wrote Apr 18, 2013 at 11:40 PM

There is a solution as found here: https://xunit.codeplex.com/discussions/211566

dparvin wrote Nov 5, 2013 at 7:50 PM

Ok. So n I have it back now? I was using the output stored with the tests and now they are gone with little feedback on how my test ran other then my asserts did not fail. I updated to the latest version and now I can't see the test output. When I run the tests in VS, any output that used to be put into the output is now swallowed and I can't see it anyplace unless I debug the test.