logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-761) Move performance tests from JUnit to log4j-perf
Date Wed, 27 Apr 2016 14:00:20 GMT

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

Matt Sicker commented on LOG4J2-761:
------------------------------------

Remko has been handling most of it. I think he wanted to keep a couple basic perf tests in
log4j-core for quick regression testing, though which ones those were I don't recall.

> 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


Mime
View raw message