accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3929) Separate performance/timing-sensitive tests from the rest of integration tests
Date Thu, 02 Jul 2015 02:42:04 GMT


Christopher Tubbs commented on ACCUMULO-3929:

Dramatic changes to the tests between bugfix releases can make it hard to compare reliability
between them. I suspect this change will be very small, but if it turns out not to be, I'd
suggest limiting the fixVersion to just the latest branch.

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