The JUnit tests produce a lot of output, even if the tests are successful.

Is there really any need to print stack traces in the following method?

TestSharedPoolDataSource.PoolTest.run()

I propose to comment them out.

Similarly, the test case TestManual.testLogWriter() generates a lot of output.
It's not clear to me what the test is trying to achieve.
Any ideas?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to