accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4423) Define categories for integration test execution
Date Thu, 25 Aug 2016 21:16:20 GMT


Josh Elser commented on ACCUMULO-4423:

Hey Dima!

No pitchforks at all! We're happy to have help where offered.

Presently, Maven still drives everything (which, personally, I like). The downside is that
it does require a little bit of configuration instead of just doing something like picking
up an hbase-site.xml and auto-bootstrapping itself off of the classpath.

We also, somewhere, have some integration that can run all of the Integration Tests we have
presently via MapReduce. I'm... not sure where the documentation on that is. I think your
approach would be nice for that. [~ecn] or [~ctubbsii], do you have anything you could point
us to on the mapreduce IT execution?

> Define categories for integration test execution
> ------------------------------------------------
>                 Key: ACCUMULO-4423
>                 URL:
>             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

View raw message