[
https://issues.apache.org/jira/browse/ACCUMULO-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437810#comment-15437810
]
Eric Newton commented on ACCUMULO-4423:
---------------------------------------
[~elserj] the code to run the IT's in a MapReduce job is
[here|https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob;f=test/src/main/java/org/apache/accumulo/test/mrit/IntegrationTestMapReduce.java;h=04d7dc79f7c7d8d7fd3531929dbb25ce4e47ada0;hb=HEAD#l47]
> Define categories for integration test execution
> ------------------------------------------------
>
> Key: ACCUMULO-4423
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4423
> Project: Accumulo
> Issue Type: Improvement
> Components: build, test
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 2.0.0
>
>
> Had a thought the other day when talking to some folks about testing.
> Our current integration tests can be broken down into two categories:
> * Encapsulated (MiniCluster only)
> * Capable of using a Standalone Accumulo instance (instead of a MiniCluster)
> with any ITs that don't have MiniClusters (if there are any), I am lumping
> them into the Encapsulated category.
> Now, if I have an environment set up which I can run these Standalone tests
> against, it would be nice to just be able to execute those tests. I could
> then run the unit tests, checkstyle, findbugs, and encapsulated integration
> tests out of band, not tied to the lifetime (and cost) of that environment
> for the Standalone tests.
> It would be nice if we can use something like JUnit categories to group these
> tests and then provide the "hooks" in the build to let users specify which
> categories are executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
