[ACCUMULO-4423] Define categories for integration test execution

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.3, 1.8.0
• Component/s: build, test
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 25/Aug/16 20:30
• Updated: 02/Sep/16 15:13
• Resolved: 02/Sep/16 15:13

Description

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.

Issue Links

• is duplicated by: ACCUMULO-3370 Integration tests runs should be controlled via junit categories
• is related to: ACCUMULO-4432 Write test to assert that all ITs are categorized
• links to: GitHub Pull Request #144

Sub-Tasks

• Annotate CyclicReplicationIT: Resolved
• plugin-it failing because expected file does not exist: Resolved
• Create SunnyDay test category: Resolved
• Fix use of deprecated Timeout JUnit rule constructor: Resolved
• Create test categories for more common groups of related tests: Resolved
• Make performance test category usage consistent with other categories: Resolved