Hi Walter, I had the same thoughts when I first started at Terracotta, but as you'll see, often bugs are very difficult to reproduce due to the distributed nature of the product. Having logging in the tests allows us often to get a good idea where the problem lies. This is mostly for the monkeys.
Take care, Geert On 30 Jul 2008, at 00:41, Walter Harley wrote: > Tim Eck wrote: >> Any reason why the <echo> of the various maven classpaths need to be >> echoed to the screen every time a system test is run? The amount of >> console output we create is big enough without a few thousand >> characters >> of classpath information that is also stored in build output files. > > I'd be delighted if we could get rid of all 'logging' output on the > screen. I'd like a successful test run to say only SUCCESS and > perhaps > the name of the test that was run. I'd like a failed test to spit out > FAILURE, the name of the test, and the exception text. Anything more > than that, I think, should go only into log files. (So, I can also > see > an argument for spitting out the path to the log files, at least for > failures.) > > Is there a logistical reason why we need all this output to go to the > console as well? If so, is there a way to have a verbose and > non-verbose mode? > > Data is not information :-) > _______________________________________________ > tc-dev mailing list > tc-dev@lists.terracotta.org > http://lists.terracotta.org/mailman/listinfo/tc-dev -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
