[jira] [Assigned] (ACCUMULO-3929) Separate performance/timing-sensitive tests from the rest of integration tests

["Josh Elser (JIRA)" <ji...@apache.org>]

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

Josh Elser reassigned ACCUMULO-3929:
------------------------------------

    Assignee: Josh Elser

> Separate performance/timing-sensitive tests from the rest of integration tests
> ------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3929
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3929
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.4, 1.7.1, 1.8.0
>
>
> Sometimes in the course of fixing bugs in Accumulo, we want to write tests that are sensitive to certain performance characteristics of the underlying hardware.
> These kinds of tests are important in helping us catch regressions, but they're not suitable to run as a normal part of the integration test suite.
> We can separate these tests by creating a special Java annotation and the Category support on the [surefire plugin|http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit.html#Using_JUnit_Categories].
> The difficulty will likely be in how we want to run these tests. It should be very straightfoward to _only_ run the performance tests. Maybe more work if we want to be able to run all the normal ITs and these performance tests. Not entirely sure. HBase's top-level pom has some examples of setting up multiple executions of the surefire-plugin.



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