Looking at the last JUnit test case I wrote, I called log4j's BasicConfigurator.configure() method inside the class constructor. That worked fine for running just that single class from Eclipse's "run ...
In running some JUnit tests I start with the following to set up Log4J:
I'm then calling the following via Commons Logging:
This doesn't print stack traces though (only the exception message).