accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3929) Separate performance/timing-sensitive tests from the rest of integration tests
Date Mon, 06 Jul 2015 22:13:05 GMT


Josh Elser commented on ACCUMULO-3929:

Also, didn't bother back-porting this to the older versions. If there's a strong need, we
can look at doing it. I followed the reasoning that the fewer the changes the better on 1.6
and 1.7.

> Separate performance/timing-sensitive tests from the rest of integration tests
> ------------------------------------------------------------------------------
>                 Key: ACCUMULO-3929
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.8.0
>         Attachments: ACCUMULO-3929-01.patch
>          Time Spent: 20m
>  Remaining Estimate: 0h
> 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|].
> 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

View raw message