© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The slowdown is because NUnit captures all log events so that they can be displayed in the Gui. This takes place at the level of NUnit's own Appender, since we can't interfere with the overall level of logging for the app.
In NUnit 2.5, the capture occurs under the console runner as well as the gui, even though it is only actually used in the gui. With NUnit 2.6, due to a previous bug fix, we no longer capture logging at all under the console runner.
Under the 2.6 Gui runner, the delay was still occuring. This is because NUnit's default level for it's own Appender is 'Error' rather
than 'Off'. In order to fix this bug, the default has been changed to 'Off' and the slowdown will only occur if you actually turn on logging.
Note that the test config file controls which log events are _sent_ to the gui, while the gui settings dialog controls which received events are displayed in a particular tab.