Trace output is disabled by default in version 2.6.2.12296
Bug #1096902 reported by
Csaba Kállai
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NUnit Framework |
Triaged
|
High
|
Charlie Poole | ||
NUnit V2 |
Fix Released
|
High
|
Charlie Poole |
Bug Description
[Issue now tracked at https:/
Before we upgraded to the mentioned version both the Debug.WriteLine and the Trace.WritLine had been written out to the output in version 2.5.9. But in the new version this is disabled by default. We found that checkbox which we can enabled this with. But there is no similar option in the nunit console. We need it because it is used in out test reult logging system.
Changed in nunit-3.0: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Charlie Poole (charlie.poole) |
tags: | added: framework |
Changed in nunitv2: | |
status: | Fix Committed → Fix Released |
description: | updated |
tags: |
added: github removed: framework |
To post a comment you must log in.
Let's clarify the bug first. If I understand you correctly, the problem is not that you can't get trace output, but that NUnit is not intercepting it. That is, if you use a TraceWriter, the trace output goes where you tell it, but your event listener addin never sees it. Is that right?
If so, it makes sense. NUnit-console has never done anything with trace output. Through at least 2.5.10, it would capture be captured anyway, which seemed to be a waste of effort. Somewhere in the 2.6 series of releases, we decided to set a flag that tells the runner not to capture any trace output.
If I understand your bug correctly, you want the output to be captured so that your addin can get it.