Unit testing must use its own logging configuration
---------------------------------------------------
Key: GEOS-1545
URL: http://jira.codehaus.org/browse/GEOS-1545
Project: GeoServer
Issue Type: Bug
Components: Global
Affects Versions: 1.6.0-RC1
Reporter: Andrea Aime
Assignee: Andrea Aime
Priority: Critical
Fix For: 1.6.0-RC2, 1.7.0-beta1
Unit testing starts and stop a mock geoserver for each unit test. This in turn makes for an incredible amount of logging be written on the output. This is getting intolerable, when a test fails it's very hard to know which one failed and in which module.
Testing should have its own logging configuration that kills these extra messages, and a method test can call to set their own logging configuration (for debugging puroposes).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira