For simple single threaded tests System.out would do the job. For a multi-threaded test I have found the logging framework to be helpful because of the thread id and the timestamps.
On Thu, Sep 20, 2018 at 1:50 PM Dale Emery <dem...@pivotal.io> wrote: > As long as the stdout is available in the test results, I’m more than > happy to avoid coupling the tests to the product logging code. > > > On Sep 20, 2018, at 1:39 PM, Galen O'Sullivan <gosulli...@pivotal.io> > wrote: > > > > I was reviewing a PR recently and noticed that we have some test code > that > > uses Logger (or LogWriter). If I understand correctly, anything logged to > > stdout will be included in the test output, and anything logged in a > DUnit > > VM will be logged with the appropriate VM number prepended in the output. > > Because logging is coupled to product code, I propose we log all test > > output to standard out (using System.out.println or such). I also propose > > we add this to the Geode style guide. > > > > Thoughts/questions/objections? > > > > Thanks, > > Galen > > > — > Dale Emery > dem...@pivotal.io > >
