nunit-core team mailing list archive

[froomax <1033967@xxxxxxxxxxxxxxxxxx>]

Hi Charlie,

My initial bug report was a bit too quick. I googled for problems with
the trace output but didn't find anything so I thought it must be a
newly introduced bug. I didn't notice that there actually is a setting
since 2.6 that has be used to explicitly enable the trace output. Sorry
for that!

But would it be possible to enable this setting by default? Everyone
here is used to first checking the trace output when there are problems
with a test (we use loggers that generate trace output while testing)..
right now / since 2.6 the setting has to be explicitly enabled or they
won't see anything.

?

Max

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/1033967

Title:
  The "Text Output" Tab doesn't display Trace-Output anymore

Status in NUnit V2 Test Framework:
  Invalid

Bug description:
  It looks like there's a problem with the "Text Output" tab in NUnit
  2.6. It doesn't display Trace.WriteLines anymore.

  The following test displays "hello world!" in the Text Output tab of
  NUnit 2.5, but in NUnit 2.6 the window stays empty:

    [TestFixture]
    public class TraceTests {
      [Test]
      public void Test() {
        Trace.WriteLine("hello world!");
      } 
    }

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/1033967/+subscriptions