accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3871) run integration tests as a map/reduce job
Date Thu, 04 Jun 2015 17:04:38 GMT


Christopher Tubbs commented on ACCUMULO-3871:

So, we're kind of already doing the "suggested way" already, by having our own test module.
This is equivalent to a separate project with one variation: the stuff in src/test/java should
be moved into src/main/java, which would also require moving test-scoped dependencies to compile
(or runtime) scope.

I think it'd be fine to just complete moving the src/test/java stuff in the test jar to src/main/java
to make all this work well. For our tests, this would mean we'd have to direct maven-failsafe-plugin
look for ITs in src/main/java instead of src/test/java. However, I don't think that would
be difficult.

It would also be convenient to have a shaded jar built in the test module (in a profile, please...
not active by default).

One thing we may want to also consider is whether we should be deploying the test module artifacts
at all. We probably never really should have been doing this, but with the move of stuff from
src/test/java to src/main/java, the resulting jar is going to be much larger (full of ITs
that are completely useless outside the build/testing of accumulo itself), so we may want
to disable this module entirely in the release profile, so it doesn't get deployed to maven

> run integration tests as a map/reduce job
> -----------------------------------------
>                 Key: ACCUMULO-3871
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: test
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>             Fix For: 1.8.0
>          Time Spent: 1h
>  Remaining Estimate: 0h
> When the functional tests were moved to java, we lost the ability to run the tests via
map/reduce.  It would be nice to run the ITs in under 2 hours. and take advantage of an entire
cluster, especially after making large sweeping changes.

This message was sent by Atlassian JIRA

View raw message