[
https://issues.apache.org/jira/browse/ACCUMULO-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437819#comment-15437819
]
Sean Busbey commented on ACCUMULO-4423:
---------------------------------------
{quote}
Michael Wall and I were casually chatting about the possibility of making
improvements to the accumulo-maven-plugin, and them perhaps making the ITs a
separate project, to make it easier to run against that plugin. It's not a
fully fleshed out idea, but it might help set up a standalone cluster to run
tests against.... maybe slightly easier.
{quote}
I trust this would be a separate repo controlled by the Apache Accumulo PMC and
not a different project?
> 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)
