Re: [DBCP] Noisy test output

2009-11-25 Thread Phil Steitz
sebb wrote: > On 25/11/2009, Phil Steitz wrote: >> sebb wrote: >> > On 23/11/2009, sebb wrote: >> >> 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? >> >> >> >> TestSharedPoo

Re: [DBCP] Noisy test output

2009-11-25 Thread sebb
On 25/11/2009, Phil Steitz wrote: > sebb wrote: > > On 23/11/2009, sebb wrote: > >> 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(

Re: [DBCP] Noisy test output

2009-11-25 Thread Phil Steitz
sebb wrote: > On 23/11/2009, sebb wrote: >> 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. >> >> Similarl

Re: [DBCP] Noisy test output

2009-11-24 Thread sebb
On 23/11/2009, sebb wrote: > 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 TestMa

[DBCP] Noisy test output

2009-11-23 Thread sebb
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