Comment 4 for bug 1096902

Wait... I'm rethinking my last note. Trace output should currently
only display at the console if you have a TraceListener that sends it
there. That should still happen, even if NUnit also captures the
output.

So the desired behavior WRT trace is:

1. Any EventListener addins get to see it to use as they want.
2. Whatever TraceListeners you have set up also receive the output.
3. In the GUI, NUnit's own EventListener, displays trace output in the
TextOutput tab, if your settings call for it.

What do you think?

On Tue, Jan 8, 2013 at 8:25 AM, Charlie Poole <email address hidden> wrote:
> It sounds like NUnit-console should turn on the capture of trace
> output, so that addins work as expected, and also display it at the
> console for backward compatibility. Does that make sense for your
> case?
>
> Charlie
>
> On Tue, Jan 8, 2013 at 3:49 AM, Csaba Kállai <email address hidden> wrote:
>> So I have talked to my colleagues again. It seem there were some
>> misunderstanding. So the real problem: the event listener can not get
>> the trace output if we use console nunit. But in the older version it
>> works.
>>
>> In case of console nunit this event is not fired:
>>
>> public void TestOutput(TestOutput testOutput)
>>
>> --
>> You received this bug notification because you are subscribed to NUnit
>> Extended Testing Platform.
>> https://bugs.launchpad.net/bugs/1096902
>>
>> Title:
>> Trace output is disabled by default in version 2.6.2.12296
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/nunit-3.0/+bug/1096902/+subscriptions