Question

I am using Log4J v2.0 Beta3 in my application for logging and I am getting log messages generated when I run my unit tests. I checked the API for some way to set the log level to something like CRITICAL but I could not find any way to change the logger configuration.

In fact, I read this on the log4j2 website:

Note that unlike Log4j 1.x, the public Log4j 2 API does not expose methods to add, modify or remove appenders and filters or manipulate the configuration in any way.

So with that said. What is the correct way to disable logging from within unit tests?

Was it helpful?

Solution

I found my answer on the log4j2 website under 'Testing in Maven'. The recommended way seems to be to place a log4j2-test.xml file in src/test/resources. Placing the xml file into this directory will cause it to be used instead of a log4j2.xml.

OTHER TIPS

You can disable logging with setting root level to off (<Root level="off"/>).

So place log4j2.xml file into src/test/resources with following content:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="warn">
    <Loggers>
        <Root level="off"/>
    </Loggers>
</Configuration>

EDIT: Removed <!DOCTYPE xml> (based on suggestion from sprynter) to make xml valid.

Both the answers from @Jbug and @Dove work as long as you are placing the file in src/test/resources of the current module. If your app depends on a library to include log42.xml it won't work for test runs since library jar won't included test classes and resources.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top