You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2016/04/27 07:55:12 UTC

[jira] [Commented] (LOG4J2-761) Move performance tests from JUnit to log4j-perf

    [ https://issues.apache.org/jira/browse/LOG4J2-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259598#comment-15259598 ] 

Ralph Goers commented on LOG4J2-761:
------------------------------------

What is going on with this issue? Are you working on it Matt?

> Move performance tests from JUnit to log4j-perf
> -----------------------------------------------
>
>                 Key: LOG4J2-761
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-761
>             Project: Log4j 2
>          Issue Type: Test
>          Components: Core
>    Affects Versions: 2.0.1
>            Reporter: Matt Sicker
>            Priority: Minor
>              Labels: benchmark, test
>
> Firstly, all the JUnit tests marked with the category:
> {code}
> @Category(PerformanceTests.class)
> {code}
> should all be ported over to the log4j-perf module. The tests marked with this category generally only output performance benchmark data and don't perform any actual unit testing of their own. Now that we have several examples of how to use [JMH|http://openjdk.java.net/projects/code-tools/jmh/], it would be a good idea to clean up our unit tests as such. This way, we don't have to waste time in the build performing benchmark tests that aren't even verified in any way.



--
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