incubator-crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-17) Split unit tests from integration tests
Date Fri, 13 Jul 2012 04:54:34 GMT


Gabriel Reid commented on CRUNCH-17:

I also rarely launch all of the automated tests from Eclipse -- however, that's due to how
long it takes to run the automated tests in Eclipse. On projects where the automated testing
can run quickly (i.e. less than 20 seconds), I run the full test suite constantly from my

My typical workflow with Crunch is running a single test class while developing on the code
that it covers, and then running the full test suite before I commit. I would *really* like
it if the full test suite would run more quickly, but that's another story (which might involve
using the MemPipeline a lot more in the automated tests).

I'm actually ok if the unit tests can be run separately only via maven (and not directly from
the IDE) -- I think that this would already be an improvement in that it would facilitate
running more tests more regularly. Having the tests split up to allow running only the unit
tests in the IDE is less important to me personally.
> Split unit tests from integration tests
> ---------------------------------------
>                 Key: CRUNCH-17
>                 URL:
>             Project: Crunch
>          Issue Type: Task
>          Components: Core
>            Reporter: Matthias Friedrich
>            Assignee: Matthias Friedrich
>              Labels: maven
> Currently, the test suite is a mix of fast unit tests and slow integration tests which
prevents developers from executing tests early and often. It should be possible to run unit
tests separately via Eclipse (or some other IDE) and Maven. Integration tests should run in
Maven's integration-test phase.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message