[jira] [Updated] (ACCUMULO-3167) Decouple MiniAccumuloCluster from integration test base class

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

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

Josh Elser updated ACCUMULO-3167:
---------------------------------
    Fix Version/s:     (was: 1.6.1)
                   1.6.2

> Decouple MiniAccumuloCluster from integration test base class
> -------------------------------------------------------------
>
>                 Key: ACCUMULO-3167
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3167
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: mini, test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>
> (apologies if I already had a ticket for this somewhere, I couldn't find it)
> Our integration tests are very nice and automated at the moment because we can use MiniAccumuloCluster to "provision" an Accumulo instance (or used a shared instance), and run a test against it. For the most part, this works well and provides an accurate test harness.
> Thus, to run integration tests, you need a sufficiently beefy machine since the same host will be running all of Accumulo as well as performing any client work. When resources are available to use, it would be nice to leverage them -- whether these are yarn, mesos, a vanila installation, etc.
> In addition to the additional computational power from using extra hardware, it also encourages us to use the public API as much as possible instead of relying on "hidden" impl methods in MiniAccumuloCluster.
> I propose making changes to the IT test base (AbstractMacIT, SimpleMacIT, ConfigurableMacIT) to add an extra step between them an test classes to allow "injection" of a more generic Accumulo "cluster" that is not associated with MAC.



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