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
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: TestOutput testOutput) /bugs.launchpad .net/bugs/ 1096902 /bugs.launchpad .net/nunit- 3.0/+bug/ 1096902/ +subscriptions
> 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(
>
> --
> You received this bug notification because you are subscribed to NUnit
> Extended Testing Platform.
> https:/
>
> Title:
> Trace output is disabled by default in version 2.6.2.12296
>
> To manage notifications about this bug go to:
> https:/