[jira] [Closed] (LOG4J2-1773) Add StatusLoggerRule to allow unit tests to set a status level

["Matt Sicker (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4J2-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker closed LOG4J2-1773.
-------------------------------
    Resolution: Fixed

Added to master.

> Add StatusLoggerRule to allow unit tests to set a status level
> --------------------------------------------------------------
>
>                 Key: LOG4J2-1773
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1773
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: API
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>             Fix For: 2.8
>
>
> In unit tests that do not use a configuration file, it would be useful to have a JUnit rule that allows the default status logger level to be set. For example, some tests are for error scenarios that spew out a lot of status messages that are expected errors and make the unit test output hard to interpret. In such tests, this rule could be used to set the level to FATAL or OFF. This could also be used for debugging purposes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org